Recordsgolanggithub.com/jackc/puddle
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
v1.3.0
linux · go@1.26
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9fe0e5655146d3ab444a3d385ac7757a2fd3221661c815acd965cd7df23e100f
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/stretchr/testify | v1.3.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| github.com/stretchr/testify | v1.8.1 | CANDIDATE Correlated change; unproven combination | contract passed | 8 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 | v1.3.0 | v1.1.3 | v0.0.0-20190608224051-11cab39313c9 |
|---|---|---|---|
| github.com/stretchr/testify | v1.3.0 | v1.3.0 | v1.7.0 |
Moved: 1 · unchanged at every release: 0
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.