CodeSampleX

Recordsnpmelectron-publish26.15.3

Change the conditions
Fixed
Runtimenode 22 Package managerpnpm 10
Filter OSwindows 11 Package version26.15.3 Symbolwhole package Architecturex64 Execution contextnode Clear filters

Current conditions

electron-publish @26.15.3windows 11 · x64 · node 22 · pnpm 10 · node

package-level total, not an API

11 of 14 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (1)

Project observations
11 / 14
Contract verifications
nothing at this coordinate
Usage records
72
Independent reporting peers
1
Failures with a captured fingerprint
0 / 3
Last recorded
2026-08-23
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 7

First observed break

26.15.3

windows · node@24.13 · moduleSystem=esm · executionContext=node

32 FAIL · stage: UNKNOWN · fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10

View exact conditions View failure cluster
Library Version Health Measured there Projects
builder-util 26.15.3 CANDIDATE Correlated change; unproven combination contract passed 14 project-days
builder-util-runtime 9.7.0 CANDIDATE Correlated change; unproven combination contract passed 14 project-days
@types/fs-extra 9.0.13 PASS All observations passed contract passed 14 project-days
aws4 1.13.2 PASS All observations passed contract passed 14 project-days
chalk 4.1.2 PASS All observations passed contract passed 13 project-days
form-data 4.0.6 PASS All observations passed contract passed 12 project-days
fs-extra 10.1.0 PASS All observations passed contract passed 14 project-days
lazy-val 1.0.5 PASS All observations passed contract passed 14 project-days
mime 2.6.0 PASS All observations passed contract passed 12 project-days

The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.

Dependency versions across releases

What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.

Library26.15.325.1.7
builder-util 26.15.3 25.1.7
builder-util-runtime 9.7.0 9.2.10
@types/fs-extra 9.0.13 9.0.13
aws4 1.13.2 —
chalk 4.1.2 4.1.2
form-data 4.0.6 —
fs-extra 10.1.0 10.1.0
lazy-val 1.0.5 1.0.5
mime 2.6.0 2.6.0

Moved: 2 · unchanged at every release: 7

An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.

Recent failure clusters