fix(deps): update shared components packages to v7 (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@patternfly/react-charts	6.94.19 -> 7.1.2
https-proxy-agent (source)	5.0.1 -> 7.0.2

---

Release Notes

patternfly/patternfly-react (@​patternfly/react-charts)

v7.1.2

Compare Source

v7.1.1

Compare Source

v7.1.0

Compare Source

v7.0.1

Compare Source

v7.0.0

Compare Source

v6.94.21

Compare Source

6.94.21 (2023-06-05)

Note: Version bump only for package @​patternfly/react-charts

v6.94.20

Compare Source

6.94.20 (2023-04-06)

Note: Version bump only for package @​patternfly/react-charts

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

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: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates 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]

⚠ 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: package-lock.json

npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: application-services-ui@0.0.2
npm WARN Found: @patternfly/patternfly@4.224.2
npm WARN node_modules/@patternfly/patternfly
npm WARN   dev @patternfly/patternfly@"5.0.2" from the root project
npm WARN   1 more (@rhoas/app-services-ui-components)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer @patternfly/patternfly@"^4.222.4" from @rhoas/app-services-ui-components@2.31.0
npm WARN node_modules/@rhoas/app-services-ui-components
npm WARN   @rhoas/app-services-ui-components@"2.31.0" from the root project
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @rhoas/app-services-ui-components@2.31.0
npm ERR! Found: @patternfly/react-charts@7.1.2
npm ERR! node_modules/@patternfly/react-charts
npm ERR!   @patternfly/react-charts@"7.1.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @patternfly/react-charts@"^6.94.15" from @rhoas/app-services-ui-components@2.31.0
npm ERR! node_modules/@rhoas/app-services-ui-components
npm ERR!   @rhoas/app-services-ui-components@"2.31.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @patternfly/react-charts@6.94.21
npm ERR! node_modules/@patternfly/react-charts
npm ERR!   peer @patternfly/react-charts@"^6.94.15" from @rhoas/app-services-ui-components@2.31.0
npm ERR!   node_modules/@rhoas/app-services-ui-components
npm ERR!     @rhoas/app-services-ui-components@"2.31.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/worker/7664f7/886976/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/worker/7664f7/886976/cache/others/npm/_logs/2023-12-06T20_21_24_616Z-debug-0.log