Recordsgolanggoogle.golang.org/protobufv1.34.2google.golang.org/protobuf/proto.Equal
Change the conditions
Current conditions
google.golang.org/protobuf/proto.Equal @v1.34.2ubuntu glibc · x64 · go 1.26 · go 1
6 of 6 passed
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- 6 / 6
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-10-15
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.34.2
linux · go@1.26
2 FAIL
· stage: PROJECT_RESOLVE
· fingerprint: sha256:e59175c98b5c0fa609edd5fd409c478db2388a0ff3fd37f555665e61201129b7
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/golang/protobuf | v1.5.0 | CANDIDATE Correlated change; unproven combination | contract passed | 13 project-days |
| github.com/google/go-cmp | v0.5.5 | CANDIDATE Correlated change; unproven combination | contract passed | 7 project-days |
| github.com/google/go-cmp | v0.5.9 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| github.com/google/go-cmp | v0.6.0 | 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 | v1.36.12 | v1.36.11 | v1.36.10 | v1.36.6 | v1.36.5 | v1.35.2 | v1.35.1 | v1.34.2 | v1.33.0 | v1.32.0 | v1.31.0 | v1.28.0 | v1.26.0 | v1.26.0-rc.1 | v1.25.0 | v1.24.0 | v1.23.0 | v1.22.0 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| github.com/golang/protobuf | v1.5.2 | v1.5.3 | v1.5.4 | v1.5.4 | v1.5.4 | v1.5.0 | v1.5.4 | v1.5.0 | v1.5.2 | v1.5.0 | v1.5.3 | v1.5.3 | v1.5.3 | — | v1.4.2 | v1.4.2 | v1.4.0 | v1.4.1 |
| github.com/google/go-cmp | v0.7.0 | v0.7.0 | v0.7.0 | v0.5.5 | v0.6.0 | v0.6.0 | v0.6.0 | v0.5.9 | v0.6.0 | v0.5.5 | v0.5.9 | v0.6.0 | v0.5.5 | v0.5.5 | v0.5.1 | v0.4.1 | v0.4.0 | v0.4.0 |
| google.golang.org/genproto | — | — | — | — | — | — | — | — | — | — | — | — | — | — | v0.0.0-20200804131852-c06518451d9c | v0.0.0-20200618031413-b414f8b61790 | — | — |
Moved: 3 · 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.
Recent failure clusters
-
observed PROJECT_RESOLVE exit 1 ×2 v1.34.2 → v1.36.6 os=linux · runtime=go@1.26 sha256:e59175c98b5c…<path> missing go.sum entry for module providing package google.golang.org/genproto/googleapis/rpc/status (imported by google.golang.<token>); to add: …go/module · resolve-diagnostic · outer go listEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-09-15