Recordsgolanggoogle.golang.org/protobufv1.36.6google.golang.org/protobuf/proto.Uint64
Change the conditions
Current conditions
google.golang.org/protobuf/proto.Uint64 @v1.36.6ubuntu 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
- Project observations
- 2 / 2
- Contract verifications
- 0 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-02
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.36.6 github.com/golang/protobuf@v1.5.0
linux · go@1.26
3 FAIL
· stage: UNKNOWN
· fingerprint: sha256:042f6e977a16262a7e633b3137ce9291be598b66496d9201e447ee2b8efa6eb8
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/golang/protobuf | v1.5.0 | FAIL Linked failure observed; version changed across releases | contract passed | 2 project-days |
| github.com/google/go-cmp | v0.5.5 | FAIL Linked failure observed; version changed across releases | 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 | v1.36.12 | v1.36.11 | v1.36.10 | v1.36.6 | v1.36.5 | v1.34.2 | v1.33.0 | v1.32.0 | v1.28.0 | v1.26.0 | v1.26.0-rc.1 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| github.com/golang/protobuf | v1.5.2 | v1.5.0 | v1.5.0 | v1.5.0 | v1.5.4 | v1.5.0 | v1.5.4 | v1.5.0 | v1.5.0 | v1.5.3 | — |
| github.com/google/go-cmp | v0.7.0 | v0.7.0 | v0.7.0 | v0.5.5 | v0.6.0 | v0.5.5 | v0.5.5 | v0.5.5 | v0.5.5 | v0.5.5 | v0.5.5 |
Moved: 2 · 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 UNKNOWN exit 1 Evidence gap ×3 v1.36.6 → v1.36.11 os=linux · runtime=go@1.26 google.golang.org/protobuf/proto.Uint64 sha256:042f6e977a16…go: updates to go.mod needed; to update it: · go mod tidygo · unclassified-diagnostic · outer go run, go test · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-09-02Diagnostic re-verification candidate
-
observed PROJECT_RESOLVE exit 1 ×1 v1.36.6 os=linux · runtime=go@1.26 sha256:b0247b83064b…<path>:<n>:<n>: missing go.sum entry for module providing package github.com/golang/protobuf/proto (imported by github.com/prometheus/client_model/go); to add: …go/module · resolve-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29
-
observed PROJECT_TEST exit 1 ×1 v1.36.6 os=linux · runtime=go@1.26 sha256:ff5e52a88cb0…FAIL example.com/metrictype [setup failed] · FAIL example.com/metrictype/test [setup failed]go/test · test-runner-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29