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

chore(deps): update dependency https-proxy-agent to v6 - autoclosed #1764

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 4, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
https-proxy-agent 5.0.1 -> 6.2.0 age adoption passing confidence

Release Notes

TooTallNate/proxy-agents

v6.2.0

Compare Source

Minor Changes
  • 8ff9faa: "headers" option can now be a function
Patch Changes
  • Updated dependencies [66b4c63]
    • agent-base@7.0.2

v6.1.0

Minor Changes
  • fd6209c: Emit "proxyConnect" event on HTTP request object (part of #​153)
  • c573dbe: Emit "proxyConnect" event on Agent instance
Patch Changes
  • 7674748: Update @types/node to v14.18.45
  • Updated dependencies [7674748]
    • agent-base@7.0.1

v6.0.0

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(
  {
    protocol: 'https:',
    hostname: 'myproxy.mydomain.com'
    port: '1234',
    username: 'proxyUser',
    password: 'proxyPass'
  },
  {
    timeout: 1000,
    headers: { 'trace', 'foo' }
  }
);
Minor Changes
  • 4333067: Add support for core keepAlive: true
Patch Changes
  • c169ced: Convert mocha tests to jest for all packages
  • 06775a8: Add test for rejectUnauthorized: false missing on request options
  • Updated dependencies [c169ced]
  • Updated dependencies [d99a7c8]
  • Updated dependencies [4333067]
    • agent-base@7.0.0

Configuration

📅 Schedule: Branch creation - "every weekday" (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.


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

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/https-proxy-agent-6.x branch from 2748c16 to 388a9ec Compare May 6, 2023 00:18
@renovate renovate bot force-pushed the renovate/https-proxy-agent-6.x branch from 388a9ec to d8fb2ee Compare May 18, 2023 21:06
@renovate renovate bot changed the title chore(deps): update dependency https-proxy-agent to v6 chore(deps): update dependency https-proxy-agent to v6 - autoclosed May 28, 2023
@renovate renovate bot closed this May 28, 2023
@renovate renovate bot deleted the renovate/https-proxy-agent-6.x branch May 28, 2023 09:38
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.

None yet

0 participants