CodeSampleX

Recordsgolanggo.uber.org/zapv1.28.0

Change the conditions
Fixed
OSwindows 11 Package versionv1.28.0
Filter Runtimego 1.26 Symbolwhole package Architecturex64 Package managergo 1 Clear filters

Current conditions

go.uber.org/zap @v1.28.0windows 11 · x64 · go 1.26 · go 1

package-level total, not an API

9 of 11 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 (14)

Project observations
9 / 11
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Failures with a captured fingerprint
0 / 2
Last recorded
2026-08-18
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 5 · Steady 1

First observed break

v1.28.0

go@1.26

5 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
github.com/stretchr/testify v1.11.1 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
github.com/stretchr/testify v1.8.1 CANDIDATE Correlated change; unproven combination contract passed 11 project-days
go.uber.org/goleak v1.3.0 CANDIDATE Correlated change; unproven combination contract passed 11 project-days
go.uber.org/multierr v1.10.0 CANDIDATE Correlated change; unproven combination contract passed 11 project-days
go.uber.org/multierr v1.11.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
go.yaml.in/yaml/v3 v3.0.4 PASS All observations passed contract passed 13 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.

Libraryv1.28.0v1.27.1v1.27.0v1.26.0v1.17.0v1.13.0
github.com/stretchr/testify v1.11.1 v1.8.1 v1.8.1 v1.8.1 v1.7.0 v1.4.0
go.uber.org/atomic — — — — v1.7.0 v1.5.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.6.0 v1.3.0
github.com/pkg/errors — — — — v0.9.1 v0.9.1
go.yaml.in/yaml/v3 v3.0.4 — — — — —
golang.org/x/lint — — — — — v0.0.0-20190930215403-16217165b5de
gopkg.in/yaml.v2 — — — — v2.4.0 —
gopkg.in/yaml.v3 — v3.0.1 v3.0.1 v3.0.1 — —

Moved: 4 · 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