Recordsgolanggithub.com/cpuguy83/go-md2man/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.0.2
linux · go@1.26
2 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/russross/blackfriday/v2 | v2.1.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 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 | v2.0.7 | v2.0.6 | v2.0.2 | v2.0.0 |
|---|---|---|---|---|
| github.com/russross/blackfriday/v2 | v2.1.0 | v2.1.0 | v2.1.0 | v2.0.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.