Recordsgolanggopkg.in/yaml.v2
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
v2.2.2
linux · go@1.26
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:6ab050d4d4b1a7c9fde83bf5cb81c7f5e71fb06a2d34da1bf7b8e6d7e8d53dcc
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| gopkg.in/check.v1 | v0.0.0-20161208181325-20d25e280405 | CANDIDATE Correlated change; unproven combination | contract passed | 13 project-days |
| gopkg.in/check.v1 | v1.0.0-20180628173108-788fd7840127 | CANDIDATE Correlated change; unproven combination | nothing measured | 24 project-days |
| gopkg.in/check.v1 | v1.0.0-20190902080502-41f04d3bba15 | CANDIDATE Correlated change; unproven combination | nothing measured | 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 | v2.4.0 | v2.3.0 | v2.2.2 | v2.2.1 |
|---|---|---|---|---|
| gopkg.in/check.v1 | v1.0.0-20190902080502-41f04d3bba15 | v0.0.0-20161208181325-20d25e280405 | v1.0.0-20190902080502-41f04d3bba15 | v0.0.0-20161208181325-20d25e280405 |
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.