Records/golang/google.golang.org/genproto/googleapis/api/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-20260825221802-da73d73af1c5 PASS 5 passing observations
• v0.0.0-20260819154853-08b0e4226688 not measured
• v0.0.0-20260720211330-0afa2a65878a not measured
• v0.0.0-20260526163538-3dc84a4a5aaa not measured
• v0.0.0-20260406210006-6f92a3bedf2d FAIL
• v0.0.0-20260401024825-9d38bb4040a9 PASS 4 passing observations
• v0.0.0-20260209200024-4cfbd4190f57 not measured
• v0.0.0-20250728155136-f173205681a0 not measured

Where it reproduced

• os=linux · runtime=go@1.26 ×1 2026-08-31 → 2026-08-31

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-20260401024825-9d38bb4040a9 → first failing release v0.0.0-20260406210006-6f92a3bedf2d

  What differs across the boundary

  • google.golang.org/genproto/googleapis/rpc v0.0.0-20260401024825-9d38bb4040a9 → v0.0.0-20260406210006-6f92a3bedf2d, v0.0.0-20260427160629-7cedc36a6bc4 hypothesis
  • google.golang.org/grpc v1.80.0 → v1.80.0, v1.81.0 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-20260406210006-6f92a3bedf2d → first passing release v0.0.0-20260825221802-da73d73af1c5

  Releases between them never measured at this stage: 3

  What differs across the boundary

  • google.golang.org/genproto/googleapis/rpc v0.0.0-20260819154853-08b0e4226688, v0.0.0-20260825221802-da73d73af1c5 → v0.0.0-20260406210006-6f92a3bedf2d, v0.0.0-20260427160629-7cedc36a6bc4 hypothesis
  • google.golang.org/grpc v1.79.3, v1.83.2 → v1.80.0, v1.81.0 hypothesis
  • google.golang.org/protobuf 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: 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.

Evidence gaps

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

Published answers for the affected releases

• google.golang.org/genproto/googleapis/api v0.0.0-20260406210006-6f92a3bedf2d: httpbody.HttpBody Built ? 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. HOWgoogle.golang.org/genproto/googleapis/api/httpbody.HttpBody MIT-0 · 2026-08-28