chore(deps): bump undici from 7.24.7 to 7.29.1

[dependabot]

Bumps undici from 7.24.7 to 7.29.1.

Release notes

Sourced from undici's releases.

v7.29.1

⚠️ Security fixes

High severity

• GHSA-w293-vg96-wgc3: BalancedPool could drop function-valued connection options while cloning its configuration, including custom TLS certificate validation callbacks. Undici now preserves connect and legacy tls options when creating upstreams. Fixed by f690157d.
• GHSA-rfgv-xxqx-mfg5: a WebSocket server could select a subprotocol when none was requested, causing an uncaught TypeError that could terminate the process. Undici now rejects the handshake with protocol error 1002. Fixed by 6615e017.

Medium severity

• GHSA-3wwx-pv8p-q78v: a malformed permessage-deflate payload exceeding the configured decompression limit could emit an unhandled zlib error and terminate the process. Undici now destroys the inflater after reaching the limit. Fixed by 63cf698b.
• GHSA-rx4f-c7p8-82vq: an unclean WebSocketStream close could create an unobserved rejected promise when its writable stream was locked, potentially terminating the process. Undici now propagates the failure through the retained writable stream controller. Fixed by 1858656e.
• GHSA-2jfj-6hjv-fm6j: shared caches could store and replay responses containing Set-Cookie, disclosing one user's cookies to another caller. Undici now excludes these responses from shared caches, including existing entries and revalidation paths. Fixed by b6c5a002.
• GHSA-3xpg-4rpp-hhhm: the decompression interceptor did not bound decoded output, allowing compressed responses to consume excessive memory. Undici now limits every decompression stage to 64 MiB by default and supports a configurable maxSize. Fixed by 2c7d7e12.
• GHSA-pmjh-fq2x-6v4x: a terminal retry failure after response headers were exposed could orphan the original response body, causing consumers to hang indefinitely. Undici now propagates the terminal error to the exposed body. Fixed by 3c672659.

Low severity

• GHSA-8436-99hf-9mmv: cache interceptors could store and replay responses to unsafe HTTP methods such as POST or DELETE. Undici now restricts cache reads and writes to safe methods while preserving invalidation by successful unsafe requests. Fixed by b61d9432.
• GHSA-2gqq-gqf2-x968: the dump interceptor could treat an oversized chunked response as successfully truncated when no Content-Length was present. Undici now enforces maxSize against received bytes and aborts oversized responses. Fixed by 21693f40.
• GHSA-r53p-7pc4-xj5r: the retry interceptor could concatenate a resumed response with inconsistent framing into downstream output, enabling response splitting or corruption. Undici now validates Content-Range against the original response framing before resuming. Fixed by cd8af90b.

What's Changed

• [v7.x] drop: remove Node.js 26 from shared-builtin CI build by @​mcollina in nodejs/undici#5592
• fix(h2): honour headersTimeout by @​mcollina in nodejs/undici#5604
• fix(h2): keep the connection ref'd while requests are outstanding by @​mcollina in nodejs/undici#5605
• ci: increase Windows workflow timeout on v7.x by @​mcollina in nodejs/undici#5621
• fix(h2): retire the request that completed, not the head of the queue by @​mcollina in nodejs/undici#5618
• fix(h2): settle a request whose stream is cancelled by @​mcollina in nodejs/undici#5607
• perf: reduce EventSourceStream parser allocations (#5032) by @​mcollina in nodejs/undici#5646
• fix(h2): handle GOAWAY for CONNECT streams by @​mcollina in nodejs/undici#5640
• [v7.x] perf(h1): drop idle-socket timer floor with a ref'd setImmediate (#5707) by @​mcollina in nodejs/undici#5769

Full Changelog: nodejs/undici@v7.29.0...v7.29.1

v7.29.0

⚠️ Security fixes

High severity

• GHSA-4cwx-7wf7-3272: malformed qualified private Cache-Control directives could cause cross-user information disclosure in shared caches or a parse-time crash. The cache parser now treats empty qualified directives conservatively and safely handles mixed qualified and unqualified directives. Fixed by 9f10f1e9, with regression coverage in 466e99d1.

Medium severity

• GHSA-m8rv-5g2x-5cg5: a malicious type property on a duck-typed blob-like HTTP/1.1 request body could inject CRLF sequences into the generated content-type header. Undici now coerces and validates the value before adding it to the request. Fixed by 33928bc2.
• GHSA-jr45-8vmc-qm54: optional whitespace around = in qualified no-cache and private directives could bypass shared-cache restrictions and disclose authenticated data across users. Cache-Control parsing now normalizes these forms and applies conservative cache decisions. Fixed by 98011a86.
• GHSA-8xcm-r25x-g524: the retry interceptor could expose a stale Content-Length after resuming a partial response, potentially causing downstream response desynchronization, hangs, or corruption. Undici now rejects partial responses whose Content-Length is inconsistent with Content-Range. Fixed by 1b5a5312, with corrected fixtures in 4a9dafb1.
• GHSA-v3r7-h72x-cjcm: unsanitized domain and unparsed values passed to setCookie() could inject cookie attributes. Undici now validates cookie domains, paths, and unparsed attributes more strictly. Fixed by 3bf91ddb.

... (truncated)

Commits

• d39a83e Bumped v7.29.1 (#5772)
• 0d88464 fix(test): remove unused EventEmitter import
• f57411b perf(h1): drop idle-socket timer floor with a ref'd setImmediate (#5707) (#5769)
• 3c67265 fix(retry): settle exposed body on terminal failure
• cd8af90 fix(retry): validate resumed response framing
• 6615e01 fix(websocket): reject unrequested subprotocols
• 2c7d7e1 fix(decompress): limit decompressed response size
• b6c5a00 fix(cache): do not cache Set-Cookie in shared caches
• 21693f4 fix(interceptor/dump): abort oversized chunked responses
• f690157 fix: preserve BalancedPool connection options
• Additional commits viewable in compare view

[coveralls]

Coverage Report for CI Build 33906209247

Coverage remained the same at 100.0%

Details

• Coverage remained the same as the base build.
• Patch coverage: No coverable lines changed in this PR.
• No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	183
Covered Lines:	183
Line Coverage:	100.0%
Relevant Branches:	52
Covered Branches:	52
Branch Coverage:	100.0%
Branches in Coverage %:	Yes
Coverage Strength:	112.01 hits per line

---

💛 - Coveralls