CodeSampleX

Recordsnpm@semantic-release/github12.0.9

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

Current conditions

@semantic-release/github @12.0.9debian glibc · x64 · node 22 · npm · node

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-14
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 14

First observed break

12.0.9

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

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

View exact conditions View failure cluster
Library Version Health Measured there Projects
@octokit/plugin-paginate-rest 14.0.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
http-proxy-agent 9.1.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
https-proxy-agent 9.1.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
@octokit/core 7.0.8 PASS All observations passed contract passed 2 project-days
@octokit/plugin-retry 8.1.1 PASS All observations passed contract passed 2 project-days
@octokit/plugin-throttling 11.0.5 PASS All observations passed contract passed 2 project-days
@semantic-release/error 4.0.0 PASS All observations passed contract passed 2 project-days
aggregate-error 5.0.0 PASS All observations passed contract passed 2 project-days
debug 4.4.3 PASS All observations passed contract passed 2 project-days
dir-glob 3.0.1 PASS All observations passed contract passed 2 project-days
issue-parser 7.0.2 PASS All observations passed contract passed 2 project-days
lodash-es 4.18.1 PASS All observations passed contract passed 2 project-days
mime 4.1.0 PASS All observations passed contract passed 2 project-days
p-filter 4.1.0 PASS All observations passed contract passed 2 project-days
tinyglobby 0.2.17 PASS All observations passed contract passed 2 project-days
undici 7.29.1 PASS All observations passed contract passed 2 project-days
url-join 5.0.0 PASS All observations passed contract passed 2 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.

Library12.0.911.0.6
@octokit/plugin-paginate-rest 14.0.0 13.2.1
http-proxy-agent 9.1.0 7.0.2
https-proxy-agent 9.1.0 7.0.6
@octokit/core 7.0.8 7.0.8
@octokit/plugin-retry 8.1.1 8.1.1
@octokit/plugin-throttling 11.0.5 11.0.5
@semantic-release/error 4.0.0 4.0.0
aggregate-error 5.0.0 5.0.0
debug 4.4.3 4.4.3
dir-glob 3.0.1 3.0.1
issue-parser 7.0.2 7.0.2
lodash-es 4.18.1 4.18.1
mime 4.1.0 4.1.0
p-filter 4.1.0 4.1.0
tinyglobby 0.2.17 0.2.17
undici 7.29.1 —
url-join 5.0.0 5.0.0

Moved: 3 · unchanged at every release: 14

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