Records/golang/google.golang.org/genproto/googleapis/rpc/failure issue

Where it was measured

PASS means the release recorded a passing observation at PROJECT_COMPILE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

• v0.0.0-20260720211330-0afa2a65878a not measured
• v0.0.0-20260715232425-e75dac1f907d PASS 3 passing observations
• v0.0.0-20260706201446-f0a921348800 FAIL
• v0.0.0-20260630182238-925bb5da69e7 PASS 3 passing observations
• v0.0.0-20260526163538-3dc84a4a5aaa not measured
• v0.0.0-20260414002931-afd174a4e478 not measured
• v0.0.0-20260406210006-6f92a3bedf2d PASS 1 passing observations
• v0.0.0-20260401024825-9d38bb4040a9 FAIL
• v0.0.0-20260401001100-f93e5f3e9f0f PASS 7 passing observations

Where it reproduced

• os=linux · runtime=go@1.26 ×4 2026-08-31 → 2026-10-12

Nearest known PASS/FAIL boundaries

The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.

• Last passing release v0.0.0-20260401001100-f93e5f3e9f0f → first failing release v0.0.0-20260401024825-9d38bb4040a9

  What differs across the boundary

  • google.golang.org/protobuf v1.36.11, v1.36.12 → v1.36.11 hypothesis

  A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.

• Last failing release v0.0.0-20260401024825-9d38bb4040a9 → first passing release v0.0.0-20260406210006-6f92a3bedf2d

  Both trees resolved every dependency to the same version. Nothing here moved.

• Last passing release v0.0.0-20260630182238-925bb5da69e7 → first failing release v0.0.0-20260706201446-f0a921348800

  What differs across the boundary

  • google.golang.org/protobuf v1.36.11, v1.36.12 → v1.36.11 hypothesis

  A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.

• Last failing release v0.0.0-20260706201446-f0a921348800 → first passing release v0.0.0-20260715232425-e75dac1f907d

  What differs across the boundary

  • google.golang.org/protobuf v1.36.11, v1.36.12 → v1.36.11 hypothesis

  A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.

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.

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

• Releases in this window never measured at PROJECT_COMPILE: 3
• No failure domain was inferred for this failure.

Published answers for the affected releases

No published sample names these releases.