Skip to content
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

Update dependency https-proxy-agent to v7 #500

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 26, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
https-proxy-agent (source) ^5.0.0 -> ^7.0.0 age adoption passing confidence

Release Notes

TooTallNate/proxy-agents (https-proxy-agent)

v7.0.6

Compare Source

Patch Changes

v7.0.5

Compare Source

Patch Changes
  • 5908e84: Remove net.isIP() check for TLS servername

v7.0.4

Compare Source

Patch Changes
  • b88ab46: Import url instead of node:url 🤷‍♂️

v7.0.3

Compare Source

Patch Changes
  • c3c405e: Add missing URL type import

v7.0.2

Compare Source

Patch Changes
  • e625d10: Support SNI for proxy servers

v7.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: Remove secureProxy getter

    It 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 proxy CONNECT response

v6.2.0

Compare Source

Minor Changes
  • 8ff9faa: "headers" option can now be a function
Patch Changes

v6.1.0

Compare Source

Minor Changes
  • fd6209c: Emit "proxyConnect" event on HTTP request object (part of #​153)
  • c573dbe: Emit "proxyConnect" event on Agent instance
Patch Changes

v6.0.0

Compare Source

Major Changes
  • d99a7c8: Major version bump for all packages
    • ⚠️ This is a breaking change! The HttpsProxyAgent 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) a string, or (B) an object matching the output of
the deprecated url.parse() method
and various extra options.

Now the constructor takes two separate arguments:

  • Argument 1: Either (A) a string, or (B) a WHATWG URL object
  • Argument 2 (optional): An object with standard http.Agent,
    net.TcpNetConnectOpts, and tls.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 move
any other options to the second argument.

5.x usage:

const agent = new HttpsProxyAgent({
  protocol: 'https:',
  host: 'myproxy.mydomain.com'
  port: '1234',
  auth: 'proxyUser:proxyPass',
  timeout: 1000,
  headers: { 'trace', 'foo' }
});

Updated 6.x usage:

const agent = new HttpsProxyAgent(
  'https://proxyUser:[email protected]:1234',
  {
    timeout: 1000,
    headers: { 'trace', 'foo' }
  }
);
Minor Changes
  • 4333067: Add support for core keepAlive: true
Patch Changes

Configuration

📅 Schedule: Branch creation - "* 0-3 * * *" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/https-proxy-agent-7.x branch 7 times, most recently from 06a793a to fa481ea Compare June 1, 2023 04:16
@renovate renovate bot force-pushed the renovate/https-proxy-agent-7.x branch 3 times, most recently from 2ecb38c to 6923641 Compare June 11, 2023 03:07
@renovate renovate bot force-pushed the renovate/https-proxy-agent-7.x branch 4 times, most recently from fb7d421 to 97ff3b6 Compare June 18, 2023 03:37
@renovate renovate bot force-pushed the renovate/https-proxy-agent-7.x branch 3 times, most recently from a3d545e to b7c709a Compare July 3, 2023 03:17
@renovate renovate bot force-pushed the renovate/https-proxy-agent-7.x branch 4 times, most recently from e5d6854 to 1e23fdb Compare July 9, 2023 04:15
@renovate renovate bot force-pushed the renovate/https-proxy-agent-7.x branch 6 times, most recently from 6c9f199 to 7ccfe6b Compare July 28, 2023 03:40
@renovate renovate bot force-pushed the renovate/https-proxy-agent-7.x branch 3 times, most recently from 96a4fcf to a13a39e Compare August 6, 2023 03:05
@renovate renovate bot force-pushed the renovate/https-proxy-agent-7.x branch 4 times, most recently from f109cdb to f0cb22e Compare October 3, 2023 04:45
@renovate renovate bot force-pushed the renovate/https-proxy-agent-7.x branch 8 times, most recently from ae287d7 to 2109dda Compare December 10, 2023 03:46
@renovate renovate bot force-pushed the renovate/https-proxy-agent-7.x branch 10 times, most recently from 8fd21cf to e226b85 Compare October 13, 2024 07:28
@renovate renovate bot changed the title Update dependency https-proxy-agent to v7 Update dependency https-proxy-agent to v7 - autoclosed Dec 8, 2024
@renovate renovate bot closed this Dec 8, 2024
@renovate renovate bot deleted the renovate/https-proxy-agent-7.x branch December 8, 2024 18:44
@renovate renovate bot changed the title Update dependency https-proxy-agent to v7 - autoclosed Update dependency https-proxy-agent to v7 Dec 13, 2024
@renovate renovate bot reopened this Dec 13, 2024
@renovate renovate bot force-pushed the renovate/https-proxy-agent-7.x branch from 7a00de2 to e226b85 Compare December 13, 2024 02:03
@renovate renovate bot force-pushed the renovate/https-proxy-agent-7.x branch from e226b85 to 8646329 Compare December 13, 2024 04:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants