Recordspypipytest
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
No recorded evidence matches these filters. Nothing is inferred; clear a filter to widen the slice.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
9.1.1
windows · python@3.10
4 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| packaging | 26.2 | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| packaging | 26.3 | CANDIDATE Correlated change; unproven combination | contract passed | 8 project-days |
| colorama | 0.4.6 | PASS All observations passed | contract passed | 13 project-days |
| iniconfig | 2.3.0 | PASS All observations passed | contract passed | 13 project-days |
| pluggy | 1.6.0 | PASS All observations passed | contract passed | 13 project-days |
| pygments | 2.20.0 | PASS All observations passed | contract passed | 12 project-days |
| pygments | 2.21.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.
| Library | 9.1.1 | 8.4.1 |
|---|---|---|
| packaging | 26.2 | 26.3 |
| colorama | 0.4.6 | 0.4.6 |
| iniconfig | 2.3.0 | 2.3.0 |
| pluggy | 1.6.0 | 1.6.0 |
| pygments | 2.21.0 | 2.21.0 |
Moved: 1 · unchanged at every release: 4
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.