Recordsgolanggithub.com/kr/pretty
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
v0.2.1
linux · go@1.26
2 FAIL
· stage: UNKNOWN
· fingerprint: sha256:00e630595b1ef857fd5ae5d542be8e69553193e64d7aa9c19d7a0623012e7f90
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/kr/text | v0.1.0 | 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 | v0.3.1 | v0.2.1 | v0.2.0 | v0.1.0 |
|---|---|---|---|---|
| github.com/kr/text | v0.2.0 | v0.1.0 | v0.1.0 | v0.1.0 |
| github.com/rogpeppe/go-internal | v1.9.0 | — | — | — |
Moved: 1 · unchanged at every release: 1
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.