CodeSampleX

Recordsnpmsemantic-release25.0.9

Change the conditions
Fixed
OSubuntu glibc Package version25.0.9 Package managernpm 10
Filter Runtimenode 22 Symbolwhole package Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

semantic-release @25.0.9ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 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 failed

Project observations
1 / 1
Contract verifications
0 / 1
Independent reporting peers
1
Last recorded
2026-09-14

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 5 · Steady 22

First observed break

25.0.9

linux · node@22.23 · executionContext=node · moduleSystem=cjs

1 FAIL · stage: UNKNOWN · fingerprint: sha256:986d98189e70ab6bb81e3ca5f5feb96281ba0dfa6e522caa6ddd3d9b148578cc

Library Version Health Measured there Projects
@semantic-release/github 12.0.9 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
@semantic-release/npm 13.1.5 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
hosted-git-info 9.0.3 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
read-package-up 12.0.0 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
yargs 18.1.0 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
@semantic-release/commit-analyzer 13.0.1 PASS All observations passed contract passed 1 project-day
@semantic-release/error 4.0.0 PASS All observations passed contract passed 1 project-day
@semantic-release/release-notes-generator 14.1.1 PASS All observations passed contract passed 1 project-day
aggregate-error 5.0.0 PASS All observations passed contract passed 1 project-day
cosmiconfig 9.0.2 PASS All observations passed contract passed 1 project-day
debug 4.4.3 PASS All observations passed contract passed 1 project-day
env-ci 11.2.0 PASS All observations passed contract passed 1 project-day
execa 9.6.1 PASS All observations passed contract passed 1 project-day
figures 6.1.0 PASS All observations passed contract passed 1 project-day
find-versions 6.0.0 PASS All observations passed contract passed 1 project-day
get-stream 6.0.1 PASS All observations passed contract passed 1 project-day
git-log-parser 1.2.1 PASS All observations passed contract passed 1 project-day
hook-std 4.0.0 PASS All observations passed contract passed 1 project-day
import-from-esm 2.0.0 PASS All observations passed contract passed 1 project-day
lodash-es 4.18.1 PASS All observations passed contract passed 1 project-day
marked 15.0.12 PASS All observations passed contract passed 1 project-day
marked-terminal 7.3.0 PASS All observations passed contract passed 1 project-day
micromatch 4.0.8 PASS All observations passed contract passed 1 project-day
p-each-series 3.0.0 PASS All observations passed contract passed 1 project-day
p-reduce 3.0.0 PASS All observations passed contract passed 1 project-day
resolve-from 5.0.0 PASS All observations passed contract passed 1 project-day
semver 7.8.5 PASS All observations passed contract passed 1 project-day

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.

Moved: 5 · unchanged at every release: 24

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