Recordsgolanggithub.com/go-kit/logv0.2.1
Change the conditions
Current conditions
github.com/go-kit/log @v0.2.1windows 11 · x64 · go 1.26 · go 1
package-level total, not an API
3 of 3 passed
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (4)
- Project observations
- 3 / 3
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-17
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.2.1
linux · go@1.26
1 FAIL · stage: PROJECT_PROCESS
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/go-logfmt/logfmt | v0.5.1 | CANDIDATE Correlated change; unproven combination | contract passed | 4 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.2.1 | v0.2.0 | v0.1.0 |
|---|---|---|---|
| github.com/go-logfmt/logfmt | v0.5.1 | v0.5.1 | v0.5.0 |
| github.com/go-stack/stack | — | — | v1.8.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.