Recordsnpmtldts-corefailure issue
Failure signature
PROJECT_TEST exit 1 ERR_ASSERTION ×1
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal: · 2 !== 0 · at TestContext.<anonymous> (<url>) …
Evidence quality: complete · javascript/test-runner · test-runner-diagnostic · First recorded: 2026-09-13 · Last seen: 2026-09-13
sha256:0cab186a142b…
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.
- 7.4.12 FAIL
- 7.4.11 not measured
- 7.4.10 PASS 1 passing observations
- 7.0.19 PASS 1 passing observations
Where it reproduced
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×1 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 passing release 7.4.10 → first failing release 7.4.12
Releases between them never measured at this stage: 1
Both trees resolved every dependency to the same version. Nothing here moved.
Evidence gaps
- Releases in this window never measured at PROJECT_TEST: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.