Recordsnpmelectron-publish
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
| node 24 | node 22 | |
|---|---|---|
| electron-publish | 89%28 | 97%38 |
| GitHubPublisher | 100%3 | |
| HttpPublisher | 83%6 | |
| Publisher | 100%4 | |
| electron-publish.HttpPublisher | 80%5 | |
| electron-publish.Publisher | 100%3 |
Showing the environments with the most evidence. The cube reads the newest 6 versions and the first 10 symbols of each, so an empty cell here can mean "outside that window" rather than "never measured".
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
First observed break
25.1.7
moduleSystem=cjs · executionContext=node
6 FAIL
· stage: UNKNOWN
· fingerprint: sha256:bc4d7ddc5bcdb4d412bf4a8bb2673c786c7e3852044dc88acdc3e1dc4e6f49cb
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| builder-util | 25.1.7 | CANDIDATE Correlated change; unproven combination | contract passed | 23 project-days |
| builder-util-runtime | 9.2.10 | CANDIDATE Correlated change; unproven combination | contract passed | 23 project-days |
| chalk | 4.1.2 | UNKNOWN No linked outcome measured | 23 project-days | |
| @types/fs-extra | 9.0.13 | PASS All observations passed | contract passed | 23 project-days |
| fs-extra | 10.1.0 | PASS All observations passed | contract passed | 23 project-days |
| lazy-val | 1.0.5 | PASS All observations passed | contract passed | 23 project-days |
| mime | 2.6.0 | PASS All observations passed | contract passed | 22 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.
| Library | 26.15.3 | 25.1.7 |
|---|---|---|
| builder-util | 26.15.3 | 25.1.7 |
| builder-util-runtime | 9.7.0 | 9.2.10 |
| @types/fs-extra | 9.0.13 | 9.0.13 |
| aws4 | 1.13.2 | — |
| chalk | 4.1.2 | 4.1.2 |
| form-data | 4.0.6 | — |
| fs-extra | 10.1.0 | 10.1.0 |
| lazy-val | 1.0.5 | 1.0.5 |
| mime | 2.6.0 | 2.6.0 |
Moved: 2 · 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.