CodeSampleX

Recordsnpmelectron-builder

Change the conditions
Fixed
Package version25.1.8 Symbolelectron-builder.createTargets
Filter Runtimenode 22 Architecturex64 Execution contextnode Clear filters

Current conditions

electron-builder.createTargets @25.1.8x64 · node 22 · node

1 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (1)

Project observations
1 / 1
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-08-27
Evidence you can open

Exact records

This slice is down to its measured combinations — the environments below are exactly what ran.

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 4 · Steady 6

First observed break

25.1.8

windows · executionContext=node

5 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
app-builder-lib 25.1.8 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
builder-util 25.1.7 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
builder-util-runtime 9.2.10 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
dmg-builder 25.1.8 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
chalk 4.1.2 PASS All observations passed contract passed 4 project-days
fs-extra 10.1.0 PASS All observations passed contract passed 4 project-days
is-ci 3.0.1 PASS All observations passed contract passed 4 project-days
lazy-val 1.0.5 PASS All observations passed contract passed 4 project-days
simple-update-notifier 2.0.0 PASS All observations passed contract passed 4 project-days
yargs 17.7.3 PASS All observations passed contract passed 4 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.8
app-builder-lib 26.15.3 25.1.8
builder-util 26.15.3 25.1.7
builder-util-runtime 9.7.0 9.2.10
dmg-builder 26.15.3 25.1.8
chalk 4.1.2 4.1.2
ci-info 4.4.0 —
fs-extra 10.1.0 10.1.0
is-ci — 3.0.1
lazy-val 1.0.5 1.0.5
simple-update-notifier 2.0.0 2.0.0
yargs 17.7.3 17.7.3

Moved: 4 · 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.