Update dependency undici to v6.11.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
undici (source)	6.9.0 -> 6.11.1

---

Release Notes

nodejs/undici (undici)

v6.11.1

Compare Source

v6.11.0

Compare Source

v6.10.2

Compare Source

What's Changed

• Do not fail test if streams support typed arrays by @​mcollina in https://github.com/nodejs/undici/pull/2978
• fix(fetch): properly redirect non-ascii location header url by @​Xvezda in https://github.com/nodejs/undici/pull/2971
• perf: Remove double-stringify in setCookie by @​peterver in https://github.com/nodejs/undici/pull/2980
• [fix #​2982] use DispatcherInterceptor type for Dispatcher#Compose by @​clovis-guillemot in https://github.com/nodejs/undici/pull/2983
• fix: make EventSource properties enumerable by @​MattBidewell in https://github.com/nodejs/undici/pull/2987
• docs: ✏️ fixed benchmark links by @​benhalverson in https://github.com/nodejs/undici/pull/2991
• fix(#​2986): bad start check by @​metcoder95 in https://github.com/nodejs/undici/pull/2992
• fix(H2 Client): bind stream 'data' listener only after received 'response' event by @​St3ffGv4 in https://github.com/nodejs/undici/pull/2985
• feat: added search input by @​benhalverson in https://github.com/nodejs/undici/pull/2993
• chore: validate responses can be consumed without a Content-Length or… by @​jacob-ebey in https://github.com/nodejs/undici/pull/2995
• fix error message by @​KhafraDev in https://github.com/nodejs/undici/pull/2998
• Revert "perf: reuse TextDecoder instance (#​2863)" by @​panva in https://github.com/nodejs/undici/pull/2999
• test: remove only by @​metcoder95 in https://github.com/nodejs/undici/pull/3001

New Contributors

• @​Xvezda made their first contribution in https://github.com/nodejs/undici/pull/2971
• @​peterver made their first contribution in https://github.com/nodejs/undici/pull/2980
• @​clovis-guillemot made their first contribution in https://github.com/nodejs/undici/pull/2983
• @​MattBidewell made their first contribution in https://github.com/nodejs/undici/pull/2987
• @​benhalverson made their first contribution in https://github.com/nodejs/undici/pull/2991
• @​St3ffGv4 made their first contribution in https://github.com/nodejs/undici/pull/2985
• @​jacob-ebey made their first contribution in https://github.com/nodejs/undici/pull/2995

Full Changelog: nodejs/undici@v6.10.0...v6.10.2

v6.10.1

Compare Source

v6.10.0

Compare Source

What's Changed

• test: fix flakyness of issue-803 test by @​Uzlopak in https://github.com/nodejs/undici/pull/2960
• Cleanup format by @​KhafraDev in https://github.com/nodejs/undici/pull/2959
• Chore: run tests daily against node nightly by @​mweberxyz in https://github.com/nodejs/undici/pull/2969
• fix: fix retry handler option by @​acommodari in https://github.com/nodejs/undici/pull/2962
• build(deps): bump node from 4999fa1 to 577f8eb in /build by @​dependabot in https://github.com/nodejs/undici/pull/2974
• feat(TS): add types for composed dispatchers by @​metcoder95 in https://github.com/nodejs/undici/pull/2967
• fix: count for error response and network errors by @​metcoder95 in https://github.com/nodejs/undici/pull/2966

New Contributors

• @​mweberxyz made their first contribution in https://github.com/nodejs/undici/pull/2969
• @​acommodari made their first contribution in https://github.com/nodejs/undici/pull/2962

Full Changelog: nodejs/undici@v6.9.0...v6.10.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.

[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: pnpm-lock.yaml

Scope: all 21 workspace projects
Progress: resolved 0, reused 1, downloaded 0, added 0
.                                        |  WARN  deprecated @babel/plugin-proposal-object-rest-spread@7.20.7
.                                        |  WARN  deprecated @types/sharp@0.32.0
Progress: resolved 118, reused 81, downloaded 0, added 0
Progress: resolved 156, reused 104, downloaded 0, added 0
packages/next                            |  WARN  deprecated @babel/plugin-proposal-class-properties@7.18.6
packages/next                            |  WARN  deprecated @babel/plugin-proposal-export-namespace-from@7.18.9
packages/next                            |  WARN  deprecated @babel/plugin-proposal-numeric-separator@7.18.6
Progress: resolved 265, reused 209, downloaded 0, added 0
packages/next                            |  WARN  deprecated @types/lru-cache@7.10.10
packages/next                            |  WARN  deprecated @types/path-to-regexp@1.7.0
/tmp/renovate/repos/github/X-oss-byte/Nextjs/packages/third-parties:
 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/next/-/next-13.5.0.tgz: Not Found - 404

This error happened while installing a direct dependency of /tmp/renovate/repos/github/X-oss-byte/Nextjs/packages/third-parties

No authorization header was set for the request.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[changeset-bot]

⚠️ No Changeset found

Latest commit: c242470

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR