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

fix(deps): update dependency https-proxy-agent to v7 #5789

Merged
merged 2 commits into from Apr 23, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 9, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
https-proxy-agent (source) 5.0.1 -> 7.0.4 age adoption passing confidence

Release Notes

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

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
  • Updated dependencies [66b4c63]
    • agent-base@7.0.2

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
  • 7674748: Update @types/node to v14.18.45
  • Updated dependencies [7674748]
    • agent-base@7.0.1

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:proxyPass@myproxy.mydomain.com:1234',
  {
    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 - "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.


  • 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 requested a review from a team as a code owner June 9, 2023 19:25
kodiakhq[bot]
kodiakhq bot previously approved these changes Jun 9, 2023
kodiakhq[bot]
kodiakhq bot previously approved these changes Jul 10, 2023
kodiakhq[bot]
kodiakhq bot previously approved these changes Jul 17, 2023
@renovate renovate bot force-pushed the renovate/https-proxy-agent-7.x branch from 45d51ab to a94a400 Compare September 4, 2023 09:11
@renovate renovate bot requested a review from a team as a code owner September 4, 2023 09:11
kodiakhq[bot]
kodiakhq bot previously approved these changes Sep 4, 2023
kodiakhq[bot]
kodiakhq bot previously approved these changes Oct 19, 2023
kodiakhq[bot]
kodiakhq bot previously approved these changes Oct 24, 2023
kodiakhq[bot]
kodiakhq bot previously approved these changes Oct 27, 2023
kodiakhq[bot]
kodiakhq bot previously approved these changes Nov 2, 2023
kodiakhq[bot]
kodiakhq bot previously approved these changes Feb 12, 2024
kodiakhq[bot]
kodiakhq bot previously approved these changes Feb 15, 2024
kodiakhq[bot]
kodiakhq bot previously approved these changes Mar 21, 2024
kodiakhq[bot]
kodiakhq bot previously approved these changes Apr 23, 2024
@renovate renovate bot force-pushed the renovate/https-proxy-agent-7.x branch from e5cf659 to 9646f8a Compare April 23, 2024 18:16
@ericapisani ericapisani self-assigned this Apr 23, 2024
Copy link

📊 Benchmark results

Comparing with c20c089

  • Dependency count: 1,348 ⬆️ 0.15% increase vs. c20c089
  • Package size: 328 MB ⬆️ 0.04% increase vs. c20c089
  • Number of ts-expect-error directives: 1,007 (no change)

@ericapisani ericapisani added the automerge Add to Kodiak auto merge queue label Apr 23, 2024
@kodiakhq kodiakhq bot merged commit b51c01c into main Apr 23, 2024
40 checks passed
@kodiakhq kodiakhq bot deleted the renovate/https-proxy-agent-7.x branch April 23, 2024 19:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge Add to Kodiak auto merge queue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant