Recordsgolanggoogle.golang.org/protobufv1.31.0google.golang.org/protobuf/proto.Int64
Change the conditions
Current conditions
google.golang.org/protobuf/proto.Int64 @v1.31.0ubuntu glibc · x64 · go 1.26 · go 1
1 of 1 passed
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- 1 / 1
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-30
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.31.0
go@1.26
6 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/golang/protobuf | v1.5.0 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| github.com/golang/protobuf | v1.5.3 | CANDIDATE Correlated change; unproven combination | builds observed | 1 project-day |
| github.com/google/go-cmp | v0.5.5 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| github.com/google/go-cmp | v0.5.9 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
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.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.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.4 | v1.5.0 | v1.5.2 | v1.5.0 | v1.5.3 | v1.5.3 | v1.5.3 | — | v1.4.2 | v1.4.3 | v1.4.1 |
| github.com/google/go-cmp | v0.7.0 | v0.7.0 | v0.7.0 | v0.7.0 | v0.6.0 | v0.6.0 | v0.5.5 | v0.6.0 | v0.5.5 | v0.5.9 | v0.6.0 | v0.5.5 | v0.5.5 | v0.5.1 | v0.4.0 | v0.4.0 |
| google.golang.org/genproto | — | — | — | — | — | — | — | — | — | — | — | — | — | v0.0.0-20200804131852-c06518451d9c | — | — |
Moved: 2 · unchanged at every release: 1
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_TEST Evidence gap ×6 v1.31.0 → v1.35.1 → v1.36.10 → v1.36.11 runtime=go@1.26Evidence quality: legacy-evidence-incomplete · Environment variants: 3 · First recorded: 2026-08-17 · Last seen: 2026-09-08Diagnostic re-verification candidate
-
observed PROJECT_COMPILE exit 1 ×1 v1.31.0 os=linux · runtime=go@1.26 sha256:26c80ce41e45…<path> cannot use family (variable of type *io_prometheus_client.MetricFamily) as <str>.Message value in argument to proto.Marshal: …go/compiler · compiler-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29
-
observed PROJECT_RESOLVE exit 1 ×1 v1.31.0 os=linux · runtime=go@1.26 sha256:c828959788d7…go: github.com/prometheus/client_model@v0.5.0: missing go.sum entry for go.mod file; to add it:go/module · resolve-diagnostic · outer goEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-30
-
observed PROJECT_COMPILE exit 1 ×1 v1.31.0 os=linux · runtime=go@1.26 sha256:299b8c6beaec…<path> cannot use mf (variable of type *io_prometheus_client.MetricFamily) as <str>.Message value in argument to proto.Marshal: …go/compiler · compiler-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31