chore(deps): Bump undici from 7.29.0 to 8.10.0

[dependabot]

Bumps undici from 7.29.0 to 8.10.0.

Release notes

Sourced from undici's releases.

v8.10.0

What's Changed

• feat: namespace h2 options by @​metcoder95 in nodejs/undici#5498
• test: update WPT expectations by @​mcollina in nodejs/undici#5587
• test: add cache/dedupe + dns re-dispatch integration tests by @​GiHoon1123 in nodejs/undici#5535
• fix(websocket): support process.unref by @​mcollina in nodejs/undici#5578
• fix(h2): ensure every request settles by @​mcollina in nodejs/undici#5603
• fix(readable): consume a body whose end has already been emitted by @​marko1olo in nodejs/undici#5617
• fix(retry): skip the content-length checkpoint for HEAD and for a 206 without content-range by @​marko1olo in nodejs/undici#5610
• fix: revert idle socket validation to setTimeout(0) to prevent stall on idle event loop by @​marceli1404 in nodejs/undici#5606
• fix(env-http-proxy-agent): match bare IPv6 addresses in no_proxy by @​marko1olo in nodejs/undici#5623
• test: handle aggregate balanced pool errors by @​marko1olo in nodejs/undici#5377
• fix(readable): keep body bytes that arrive after setEncoding() by @​mcollina in nodejs/undici#5620
• fix(socks5): evict unused origin pools by @​Kkartik14 in nodejs/undici#5595
• fix: skip deduplication for upgrade requests by @​Ram-blip in nodejs/undici#5593
• fix(retry): forward informational responses by @​mcollina in nodejs/undici#5625
• fix(mock): non-string path matchers under ignoreTrailingSlash, and DataView reply bodies by @​marko1olo in nodejs/undici#5619
• fix(interceptors): cache() and deduplicate() silently inert on Client/Pool without opts.origin by @​marko1olo in nodejs/undici#5628
• build(deps): bump ossf/scorecard-action from 2.4.3 to 2.4.4 by @​dependabot[bot] in nodejs/undici#5633
• build(deps): bump github/codeql-action/init from 4.36.2 to 4.37.3 by @​dependabot[bot] in nodejs/undici#5634
• build(deps): bump actions/setup-node from 6.4.0 to 7.0.0 by @​dependabot[bot] in nodejs/undici#5636
• fix(mock): emit request body lifecycle hooks by @​marko1olo in nodejs/undici#5367
• fix(h2): detach upgrade close handler after GOAWAY by @​pacocartones in nodejs/undici#5641
• fix: retry refused HTTP/2 streams by @​mcollina in nodejs/undici#5598
• fix: preserve DNS origin hostname on sockets by @​cyphercodes in nodejs/undici#5577

New Contributors

• @​marceli1404 made their first contribution in nodejs/undici#5606
• @​Kkartik14 made their first contribution in nodejs/undici#5595
• @​pacocartones made their first contribution in nodejs/undici#5641
• @​cyphercodes made their first contribution in nodejs/undici#5577

Full Changelog: nodejs/undici@v8.9.0...v8.10.0

v8.9.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 4fe5bc5f with regression coverage in 9f09b49a.

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 7d3cf924.
• 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 c601fff1.
• 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 e11a68ed, with corrected fixtures in 2b3f7493.
• 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 10d93fc3.

Additional hardening

... (truncated)

Commits

• c8d80e6 Bumped v8.10.0 (#5644)
• 66923b4 fix: preserve DNS origin hostname on sockets (#5577)
• 3926499 fix: retry refused HTTP/2 streams (#5598)
• 73d6e9e fix(h2): detach upgrade close handler after GOAWAY (#5641)
• b111adb fix(mock): emit request body lifecycle hooks (#5367)
• ae4a3e3 build(deps): bump actions/setup-node from 6.4.0 to 7.0.0 (#5636)
• ec3fbf1 build(deps): bump github/codeql-action/init from 4.36.2 to 4.37.3 (#5634)
• 2151720 build(deps): bump ossf/scorecard-action from 2.4.3 to 2.4.4 (#5633)
• b96a116 fix(interceptors): allow interceptors without opts.origin (#5628)
• a18ef2d fix(mock): non-string path matchers under ignoreTrailingSlash, and DataView r...
• Additional commits viewable in compare view

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details
npm/undici	8.10.0	🟢 7.7	Details Check Score Reason Security-Policy 🟢 10 security policy file detected Dependency-Update-Tool 🟢 10 update tool detected Code-Review 🟢 10 all changesets reviewed Maintained 🟢 10 30 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10 Binary-Artifacts 🟢 8 binaries present in source code Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected Pinned-Dependencies 🟢 6 dependency not pinned by hash detected -- score normalized to 6 Vulnerabilities ⚠️ 0 10 existing vulnerabilities detected SAST 🟢 10 SAST tool is run on all commits License 🟢 10 license file detected Fuzzing 🟢 10 project is fuzzed Signed-Releases ⚠️ -1 no releases found Packaging 🟢 10 packaging workflow detected Branch-Protection ⚠️ -1 internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md CI-Tests 🟢 10 30 out of 30 merged PRs checked by a CI test -- score normalized to 10 Contributors 🟢 10 project has 62 contributing companies or organizations

Scanned Files

• package-lock.json

[windkh]

@dependabot rebase

[dependabot]

Looks like undici is no longer being updated by Dependabot, so this is no longer needed.

[windkh]

Closing unmerged — undici 8 is not usable by this package yet, and it is not a Node-version problem.

After master dropped Node 20 (V19.0.0, ADR 0010) and this PR was rebased onto the new [22.x, 24.x] matrix, it still failed — on both legs:

Test file	Symptom
test/integration/polling.test.js	test timed out after 30000ms
test/integration/sending.test.js	test timed out after 30000ms
test/integration/setwebhook.test.js	EFATAL: fetch failed (3 subtests)
test/integration/webhook.test.js	waitFor timed out

Every failure is a request that goes out and never comes back.

Why. telegrambot/lib/undici-pool.js builds new Agent(...) from the standalone undici package, and node-telegram-bot-api spreads request.fetchOptions into a call to Node's built-in fetch — which comes from Node's own bundled undici, not ours. undici v8.0.0 removed the legacy dispatcher handler wrappers that the bundled copy still drives a dispatcher through. The dispatcher is accepted (dispatch() is reached, which is why the undici-pool unit test kept passing — it asserts only that, and swallows network errors), but the response is never delivered back.

Two undici majors cannot be mixed across the built-in-fetch boundary. This will become mergeable once a Node release bundles undici 8; process.versions.undici on the minimum supported Node is the thing to check.

undici stays at ^7, and .github/dependabot.yml now ignores its major updates so this PR does not reopen weekly. Minor and patch updates still flow, so security fixes are not blocked.

Full reasoning: ADR 0011.

[windkh]

Follow-up: the diagnosis above has now been verified directly, not just inferred.

When this was closed, the reasoning rested on the CI failure pattern plus undici's release notes. A machine with Node 24.19 was available afterwards, so the claim could be tested. It holds — and the mechanism is more precise than originally described.

Against a local HTTP server, with undici@8.10.0 installed over the tree:

node v24.19.0 | bundled undici 7.29.0 | standalone undici 8.10.0

OK     builtin fetch, no dispatcher         : 200 "pong"
FAIL   builtin fetch, undici-8 dispatcher   : TypeError: fetch failed
                                              (cause: invalid onRequestStart method)
       -> dispatch() reached: true
OK     undici-8 fetch, undici-8 dispatcher  : 200 "pong"

• The server is reachable, so the failure is not environmental.
• Our production path is the broken one. dispatch() is reached — which is why test/lib/undici-pool.test.js kept passing — but undici 8 then rejects the legacy-shaped handler Node's bundled undici hands it: invalid onRequestStart method. That is a rejection, not the silent non-delivery I described earlier; it surfaces as fetch failed, and to node-telegram-bot-api as EFATAL: fetch failed.
• undici 8 itself is fine — its own fetch drives the very same dispatcher to a 200.

The full suite agrees: 14 integration subtests pass on undici@7, zero on undici@8, with the same 0 !== 1 and EFATAL: fetch failed assertions seen here.

One number worth recording: Node 24.19.0 still bundles undici 7.29.0 — the newest line in our CI matrix. The wait for a bundled undici 8 is real, so the Dependabot ignore rule is not about to become stale.

Nothing changed in package.json or package-lock.json; undici 8 was installed with --no-save and rolled back. ADR 0011 now carries the proof.