Recordsgolanggoogle.golang.org/protobuffailure issue
Failure signature
PROJECT_RESOLVE exit 1 ×2
<path> missing go.sum entry for module providing package google.golang.org/genproto/googleapis/rpc/status (imported by google.golang.<token>); to add: …
Evidence quality: complete · go/module · resolve-diagnostic · outer go list · First recorded: 2026-08-31 · Last seen: 2026-09-15
sha256:e59175c98b5c…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_RESOLVE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- v1.36.10 not measured
- v1.36.8 not measured
- v1.36.6 FAIL
- v1.36.5 not measured
- v1.36.3 not measured
- v1.35.1 not measured
- v1.34.2 FAIL
- v1.34.1 not measured
- v1.33.0 not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×2 2026-08-31 → 2026-09-15
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
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.10 | v1.36.6 | v1.36.5 | v1.35.1 | v1.34.2 | v1.33.0 |
|---|---|---|---|---|---|---|
| github.com/golang/protobuf | v1.5.4 | v1.5.4 | v1.5.4 | v1.5.4 | v1.5.0 | v1.5.2 |
| github.com/google/go-cmp | v0.7.0 | v0.7.0 | v0.6.0 | v0.6.0 | v0.5.5 | v0.6.0 |
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.
Evidence gaps
- No release in this window recorded a passing observation at PROJECT_RESOLVE.
- Releases in this window never measured at PROJECT_RESOLVE: 7
- No failure domain was inferred for this failure.
Published answers for the affected releases
- google.golang.org/protobuf v1.34.2: Pack and unpack heterogeneous Protocol Buffers messages using anypb New, UnmarshalTo, UnmarshalNew, and MessageIs with type URL validation This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWanypb.MessageIsanypb.Newanypb.UnmarshalNewanypb.UnmarshalTo MIT-0 · 2026-08-27