Recordsgolanggo.uber.org/goleak
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: PROJECT_TEST
· fingerprint: sha256:2b1cd55a358000c17d483656568fc2dee859d7d129e76ec841f2159b73497c1c
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/stretchr/testify | v1.10.0 | CANDIDATE Correlated change; unproven combination | builds observed | 7 project-days |
| github.com/stretchr/testify | v1.11.1 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| github.com/stretchr/testify | v1.8.0 | CANDIDATE Correlated change; unproven combination | builds observed | 3 project-days |
| github.com/stretchr/testify | v1.8.1 | CANDIDATE Correlated change; unproven combination | contract passed | 13 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.2.0 |
|---|---|---|
| github.com/stretchr/testify | v1.8.0 | v1.8.1 |
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.