Update dependency https-proxy-agent to v9

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
https-proxy-agent (source)	^2.2.3 → ^9.0.0

---

Release Notes

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

v9.0.0

Compare Source

Major Changes

• 7d12b51: Set minimum Node.js version to 20

Patch Changes

• 7ca27d0: Simplify package.json exports to remove unnecessary imports restriction
• Updated dependencies [ca12148]
• Updated dependencies [7d12b51]
• Updated dependencies [7ca27d0]
  • agent-base@​9.0.0

v8.0.0

Compare Source

Major Changes

• 9c92c09: Convert to ESM. All packages now use "type": "module" and compile to ESM output instead of CommonJS.

Patch Changes

• Updated dependencies [9c92c09]
  • agent-base@​8.0.0

v7.0.6

Compare Source

Patch Changes

• 913a49a: Only overwrite servername in tls connect when host is not an IP address
• Updated dependencies [1699a09]
  • agent-base@​7.1.2

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

• 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

v5.0.1

Compare Source

Patches

• Remove servername check: 3d2981c
• Fix compatibility with Node.js 14: #​104

Credits

Huge thanks to @​lpinca for helping!

v5.0.0

Compare Source

Major Changes

• Refactor to TypeScript: #​95

v4.0.0

Compare Source

Major Changes

• Set "engines" requirement to node 6.0.0: #​82
• Update dependencies: c846a68

Minor Changes

• Update debug to v4.0.0: #​82

Patches

• Use localhost instead of 127.0.0.1 in tests: 829905f

Credits

Huge thanks to @​Krinkle for helping!

v3.0.1

Compare Source

Patches

• Update proxy to v1.0.1: 7ce932a
• Add GitHub Actions for Node CI: 67f71c6
• Delete .travis.yml: 3b680ba
• Replace Travis CI status badge with workflow status badge: #​80
• Use a net.Socket instead of a plain EventEmitter for replaying proxy errors: #​83
• Test CI on "push to master" and "pull request": 11d4677

Credits

Huge thanks to @​lpinca for helping!

v3.0.0

Compare Source

This release fixes the MitM vulnerability reported via HackerOne. It is a breaking change because Node 4, 5, and 7 are no longer tested in CI (note that Node 6 is still supported).

Major Changes

• Remove Node 5 and 7 from Travis: 590bc8b
• Remove Node 4 from Travis: 6c804a2

Minor Changes

• Update proxy to v1.0.0: d0e3c18
• Test on Node.js 10 and 12: 3535951
• Fix compatibility with Node.js >= 10.0.0: #​73
• Add .editorconfig file: 06ead2f
• Add .eslintrc.js file: ae53572

Patches

• Update README with correct secureProxy behavior: #​65
• Remove unreachable code: 46aad09
• [TypeScript] Allow port to be a string: #​72
• Use an EventEmitter to replay failed proxy connect HTTP requests: #​77

Credits

Huge thanks to @​lpinca, @​stoically, and @​zkochan for helping!

---

Configuration

📅 Schedule: (in timezone Europe/London)

• Branch creation
  • Between 04:00 PM and 07:59 PM, Monday through Friday (* 16-19 * * 1-5)
• Automerge
  • Between 02:00 PM and 06:59 PM, Monday through Thursday (* 14-18 * * 1-4)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[hmcts-jenkins-a-to-c]

Plan Result (aat)

No changes. Your infrastructure matches the configuration.

[hmcts-jenkins-a-to-c]

Plan Result (prod)

No changes. Your infrastructure matches the configuration.