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 #131

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 29, 2024

Mend Renovate

This PR contains the following updates:

Package Type Update Change OpenSSF
https-proxy-agent (source) dependencies major ^5.0.1 -> ^7.0.0 OpenSSF Scorecard

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 - At any time (no schedule defined), 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.

Copy link
Author

renovate bot commented Mar 29, 2024

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
Scope: all 14 projects
Progress: resolved 1, reused 0, downloaded 0, added 0
undefined
/tmp/renovate/repos/github/stainless-api/release-please/test/fixtures/plugins/node-workspace/node1:
 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/anotherExternal: Not Found - 404

This error happened while installing a direct dependency of /tmp/renovate/repos/github/stainless-api/release-please/test/fixtures/plugins/node-workspace/node1

anotherExternal is not in the npm registry, or you have no permission to fetch it.

No authorization header was set for the request.

@renovate renovate bot force-pushed the renovate/https-proxy-agent-7.x branch 3 times, most recently from 5ba770d to 1bbd5e5 Compare March 29, 2024 15:47
@renovate renovate bot force-pushed the renovate/https-proxy-agent-7.x branch from 1bbd5e5 to 2034f67 Compare March 29, 2024 15:54
@dgellow dgellow closed this Mar 29, 2024
Copy link
Author

renovate bot commented Mar 29, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 7.x releases. But if you manually upgrade to 7.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

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.

1 participant