CodeSampleX

Recordsnpm@semantic-release/github

no sample at this coordinate yet

Compatibility cube

Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.

Fixed
Package version12.0.9 Architecturex64
Filter Runtimenode 22 Symbolwhole package Execution contextnode libcglibc Clear filters
OS × Package manager
1○ 12026-09-14
How to read the grid

Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.

  • no sample at this coordinate yet
  • there is a sample here, and nothing of ours has run it at this coordinate yet
  • there is a sample here, and our run of it at this coordinate came back clean
  • there is a sample here, and our run of it at this coordinate failed
  • there is a sample here, and this coordinate records both a passing and a failing run of it
  • nothing recorded — unknown, never "works" and never "broken"
  • there is a level below this cell — click to open it

A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.

Cells are aggregates of everything still varying in this slice (the n/m count says how much). Click one to pin its coordinates and see the next level.

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 · moduleSystem=cjs · executionContext=node

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

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.

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.