-
Notifications
You must be signed in to change notification settings - Fork 368
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(deps): update dependency https-proxy-agent to v7 #5789
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/https-proxy-agent-7.x
branch
from
July 10, 2023 20:54
231b589
to
5c3b688
Compare
renovate
bot
force-pushed
the
renovate/https-proxy-agent-7.x
branch
from
July 17, 2023 01:57
5c3b688
to
45d51ab
Compare
renovate
bot
force-pushed
the
renovate/https-proxy-agent-7.x
branch
from
September 4, 2023 09:11
45d51ab
to
a94a400
Compare
renovate
bot
force-pushed
the
renovate/https-proxy-agent-7.x
branch
from
October 19, 2023 13:20
a94a400
to
b4a64e2
Compare
renovate
bot
force-pushed
the
renovate/https-proxy-agent-7.x
branch
from
October 24, 2023 14:09
b4a64e2
to
f552fef
Compare
renovate
bot
force-pushed
the
renovate/https-proxy-agent-7.x
branch
from
October 27, 2023 15:28
f552fef
to
54c45e7
Compare
renovate
bot
force-pushed
the
renovate/https-proxy-agent-7.x
branch
from
November 2, 2023 10:39
54c45e7
to
d358480
Compare
renovate
bot
force-pushed
the
renovate/https-proxy-agent-7.x
branch
from
February 12, 2024 18:56
d358480
to
647c05f
Compare
renovate
bot
force-pushed
the
renovate/https-proxy-agent-7.x
branch
from
February 15, 2024 22:52
647c05f
to
2c9f492
Compare
renovate
bot
force-pushed
the
renovate/https-proxy-agent-7.x
branch
from
March 20, 2024 23:17
2c9f492
to
1e27227
Compare
renovate
bot
force-pushed
the
renovate/https-proxy-agent-7.x
branch
from
April 23, 2024 16:09
1e27227
to
2c15d77
Compare
renovate
bot
force-pushed
the
renovate/https-proxy-agent-7.x
branch
from
April 23, 2024 18:16
e5cf659
to
9646f8a
Compare
ericapisani
approved these changes
Apr 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
5.0.1
->7.0.4
Release Notes
TooTallNate/proxy-agents (https-proxy-agent)
v7.0.4
Compare Source
Patch Changes
b88ab46
: Importurl
instead ofnode:url
🤷♂️v7.0.3
Compare Source
Patch Changes
c3c405e
: Add missingURL
type importv7.0.2
Compare Source
Patch Changes
e625d10
: Support SNI for proxy serversv7.0.1
Compare Source
Patch Changes
23fe1e3
: Correct the header parsing logic to stop before the response content to avoid generating an exception.v7.0.0
Compare Source
Major Changes
b3860aa
: RemovesecureProxy
getterIt was not meant to be a public property. If you were using it, just use
agent.proxy.protocol === 'https:'
instead.v6.2.1
Compare Source
Patch Changes
0b8a0b7
: Properly reject errors during proxyCONNECT
responsev6.2.0
Compare Source
Minor Changes
8ff9faa
: "headers" option can now be a functionPatch Changes
66b4c63
]v6.1.0
Compare Source
Minor Changes
fd6209c
: Emit "proxyConnect" event on HTTPrequest
object (part of #153)c573dbe
: Emit "proxyConnect" event on Agent instancePatch Changes
7674748
: Update@types/node
to v14.18.457674748
]v6.0.0
Compare Source
Major Changes
d99a7c8
: Major version bump for all packagesHttpsProxyAgent
constructor argument has been split into two arguments.Upgrading from 5.x to 6.x
In version 5.x, the
HttpsProxyAgent
constructor took a single argument of either (A) astring
, or (B) an object matching the output ofthe deprecated
url.parse()
methodand various extra options.
Now the constructor takes two separate arguments:
string
, or (B) a WHATWGURL
objecthttp.Agent
,net.TcpNetConnectOpts
, andtls.ConnectionOptions
properties and/or custom options supported by this package.If you were using an object argument in 5.x, you'll need to change the first argument to match the structure of the
URL
class, and moveany other options to the second argument.
5.x usage:
Updated 6.x usage:
Minor Changes
4333067
: Add support for corekeepAlive: true
Patch Changes
c169ced
: Convert mocha tests to jest for all packages06775a8
: Add test forrejectUnauthorized: false
missing on request optionsc169ced
]d99a7c8
]4333067
]Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.