build(deps): bump undici from 7.29.0 to 7.29.1

[dependabot]

Bumps undici from 7.29.0 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

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

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	undici@​7.29.0 ⏵ 7.30.0		+30	+1

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Priority	Alert  (click "▶" to expand/collapse)	Action
	Recently published: npm undici published 5 days ago Location: Package overview From: package.json → npm/undici@7.30.0 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/undici@7.30.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Block

View full report

[dsanders11]

@dependabot recreate

[claude]

Approve — this is a routine dependabot lockfile-only version bump for undici, well within the declared semver range.
Reviewed: the diff touches only the single undici entry in yarn.lock (version + checksum), no other files changed. Confirmed undici is a direct dependency (^7.24.4 in package.json) and 7.30.0 satisfies that range. No code paths changed, so no injection/auth/data-exposure surface to assess.

Extended reasoning...

The change is a dependabot-authored yarn.lock diff bumping undici's resolved version/checksum from 7.29.0 to 7.30.0; no source files changed. Undici is a direct dependency declared as ^7.24.4 in package.json, and 7.30.0 satisfies that range, so the bump is mechanical and low-risk. The PR title/description reference bumping to 7.29.1, but the actual lockfile targets the newer 7.30.0 — consistent with a maintainer (dsanders11) prompting dependabot to rebase onto the latest compatible release before merge, not a discrepancy in the code itself. No CODEOWNERS individual conflict, no unresolved CHANGES_REQUESTED review, and the bug hunter found no issues, so this is safe to approve without further human review.