Recordsgolanggo.uber.org/zapv1.13.0go.uber.org/zap.AtomicLevel
Change the conditions
Current conditions
go.uber.org/zap.AtomicLevel @v1.13.0ubuntu glibc · x64 · go 1.26 · go 1
0 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed (1)
- Project observations
- 3 / 3
- Contract verifications
- 0 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-15
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.13.0
linux · go@1.26
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:cc6da42c69d5a8040f6a9dbda27d7d8e0daef42f5c34d1da8e73713061384c8d
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/stretchr/testify | v1.4.0 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| github.com/stretchr/testify | v1.7.0 | CANDIDATE Correlated change; unproven combination | contract passed | 7 project-days |
| github.com/stretchr/testify | v1.8.1 | CANDIDATE Correlated change; unproven combination | contract passed | 11 project-days |
| go.uber.org/multierr | v1.3.0 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| go.uber.org/multierr | v1.5.0 | CANDIDATE Correlated change; unproven combination | contract passed | 16 project-days |
| github.com/pkg/errors | v0.8.1 | PASS All observations passed | contract passed | 21 project-days |
| github.com/pkg/errors | v0.9.1 | PASS All observations passed | contract passed | 1 project-day |
| go.uber.org/atomic | v1.5.0 | PASS All observations passed | contract passed | 4 project-days |
| go.uber.org/atomic | v1.6.0 | PASS All observations passed | contract passed | 16 project-days |
| golang.org/x/lint | v0.0.0-20190930215403-16217165b5de | PASS All observations passed | contract passed | 20 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 | v1.28.0 | v1.27.1 | v1.27.0 | v1.26.0 | v1.13.0 |
|---|---|---|---|---|---|
| github.com/stretchr/testify | v1.11.1 | v1.8.1 | v1.8.1 | v1.8.1 | v1.4.0 |
| go.uber.org/goleak | v1.3.0 | v1.3.0 | v1.3.0 | v1.2.0 | — |
| go.uber.org/multierr | v1.11.0 | v1.11.0 | v1.10.0 | v1.10.0 | v1.3.0 |
| github.com/pkg/errors | — | — | — | — | v0.9.1 |
| go.uber.org/atomic | — | — | — | — | v1.5.0 |
| go.yaml.in/yaml/v3 | v3.0.4 | — | — | — | — |
| golang.org/x/lint | — | — | — | — | v0.0.0-20190930215403-16217165b5de |
| gopkg.in/yaml.v3 | — | v3.0.1 | v3.0.1 | v3.0.1 | — |
Moved: 3 · unchanged at every release: 5
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.
Recent failure clusters
-
observed UNKNOWN exit 1 ERROR Evidence gap ×1 v1.13.0 os=linux · runtime=go@1.26 go.uber.org/zap.AtomicLevel sha256:cc6da42c69d5…go: downloading go.uber.org/zap v1.13.0 · verifying go.uber.org/zap@v1.13.0: checksum mismatch · downloaded: h1:<token> · go.sum: h1:<token>go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-15 · Last seen: 2026-09-15Diagnostic re-verification candidate