Recordsnpmsemantic-release
there is a sample for this release and API (1)
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
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
Dependency changes observed: 5. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @semantic-release/github | 11.0.6 | CHANGED Version changed, no linked failure | builds observed | 1 project-day |
| @semantic-release/npm | 12.0.2 | CHANGED Version changed, no linked failure | builds observed | 1 project-day |
| hosted-git-info | 8.1.0 | CHANGED Version changed, no linked failure | builds observed | 3 project-days |
| read-package-up | 11.0.0 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| yargs | 17.7.3 | CHANGED Version changed, no linked failure | 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 | 3 project-days |
| 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 | 3 project-days |
| semver-diff | 5.0.0 | PASS All observations passed | builds observed | 1 project-day |
| signale | 1.4.0 | 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.