Records/npm/undici/failure issue

Where it was measured

PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

• 8.10.0 PASS 6 passing observations
• 8.4.1 PASS 1 passing observations
• 7.29.1 not measured
• 7.29.0 FAIL
• 7.28.0 PASS 1 passing observations
• 6.28.1 PASS 1 passing observations
• 6.28.0 FAIL

Where it reproduced

• executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×4 2026-09-13 → 2026-09-13

Nearest known PASS/FAIL boundaries

The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.

• Last failing release 6.28.0 → first passing release 6.28.1

  Both trees resolved every dependency to the same version. Nothing here moved.

• Last passing release 7.28.0 → first failing release 7.29.0

  One side of this boundary has no resolved dependency tree, so nothing could be compared.

• Last failing release 7.29.0 → first passing release 8.4.1

  Releases between them never measured at this stage: 1

  One side of this boundary has no resolved dependency tree, so nothing could be compared.

Evidence gaps

• Releases in this window never measured at PROJECT_TEST: 1
• No resolved dependency tree for 7.28.0 or for 7.29.0, so the versions either side of the boundary could not be compared.
• No failure domain was inferred for this failure.

Published answers for the affected releases

• undici 7.29.0: request, stream, Client Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWrequeststreamClientPoolMockAgentsetGlobalDispatchererrors.MockNotMatchedErrornode 22.23.2 MIT-0 · 2026-08-28
• undici 7.29.0: Retry fetch requests with bodies safely and avoid cross-realm TypeError between undici and global fetch Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWfetchRequestResponseHeadersRequest.cloneRequest.bodyUsednode MIT-0 · 2026-08-15
• undici 6.28.0: Stream response chunks with backpressure, opaque metadata, error propagation, and abort handling using undici.stream in undici 6.28.0 Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWundici.streamnode 22.23.2 MIT-0 · 2026-08-27
• undici 6.28.0 Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWnode 22.23.2 MIT-0 · 2026-08-20