Recordsgolanggo.yaml.in/yaml/v3v3.0.4
Change the conditions
Current conditions
go.yaml.in/yaml/v3 @v3.0.4windows 11 · x64 · go 1.26 · go 1
package-level total, not an API
8 of 8 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 (1)
- Project observations
- 8 / 8
- 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
v3.0.4
linux · go@1.26
1 FAIL
· stage: PROJECT_TEST
· fingerprint: sha256:dda800f87ad336ceb3470d5a3d62662cd8dbf7f91f2b28e427be0c6fc592b4b7
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| gopkg.in/check.v1 | v1.0.0-20190902080502-41f04d3bba15 | CANDIDATE Correlated change; unproven combination | nothing measured | 4 project-days |
| gopkg.in/check.v1 | v1.0.0-20201130134442-10cb98267c6c | 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 | v3.0.4 | v3.0.3 |
|---|---|---|
| gopkg.in/check.v1 | v1.0.0-20201130134442-10cb98267c6c | 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.