Records/golang/google.golang.org/protobuf/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.

• v1.36.12 FAIL
• v1.36.11 FAIL
• v1.36.10 PASS 1 passing observations
• v1.36.8 not measured
• v1.28.0 not measured
• v1.27.1 PASS 5 passing observations
• v1.26.0 FAIL
• v1.26.0-rc.1 not measured
• v1.25.0 PASS 3 passing observations

Where it reproduced

• os=linux · runtime=go@1.26 ×6 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 v1.25.0 → first failing release v1.26.0

  Releases between them never measured at this stage: 1

  What differs across the boundary

  • github.com/golang/protobuf v1.4.1, v1.4.2, v1.4.3 → v1.5.2, v1.5.3 hypothesis
  • github.com/google/go-cmp v0.5.0, v0.5.1 → v0.5.5 hypothesis
  • google.golang.org/genproto v0.0.0-20200526211855-cb27e3aa2013, v0.0.0-20200729003335-053ba62fc06f, v0.0.0-20200804131852-c06518451d9c, v0.0.0-20200825200019-8632dd797987 → — 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 v1.26.0 → first passing release v1.27.1

  What differs across the boundary

  • github.com/golang/protobuf v1.5.2 → v1.5.2, v1.5.3 hypothesis
  • github.com/google/go-cmp v0.5.5, v0.5.6, v0.5.9 → v0.5.5 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 passing release v1.36.10 → first failing release v1.36.11

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

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: 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.

Evidence gaps

• The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
• The captured output could not establish: diagnostic-missing.
• Releases in this window never measured at PROJECT_COMPILE: 3
• No failure domain was inferred for this failure.

Published answers for the affected releases

• google.golang.org/protobuf v1.36.12: Merge, clone, equality, and reset semantics for Protocol Buffers messages across presence types, repeated slices, maps, and floating-point values 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/protobuf/proto.Mergegoogle.golang.org/protobuf/proto.Equalgoogle.golang.org/protobuf/proto.Clonegoogle.golang.org/protobuf/proto.Resetgoogle.golang.org/protobuf/reflect/protoreflect.Message.Hasgo MIT-0 · 2026-08-17
• google.golang.org/protobuf v1.36.12: Control JSON formatting and parsing of Protocol Buffers messages using protojson MarshalOptions and UnmarshalOptions 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/protobuf/encoding/protojson.Marshalgoogle.golang.org/protobuf/encoding/protojson.MarshalOptionsgoogle.golang.org/protobuf/encoding/protojson.Unmarshalgoogle.golang.org/protobuf/encoding/protojson.UnmarshalOptionsgo MIT-0 · 2026-08-17
• google.golang.org/protobuf v1.36.11: prototext.Marshal 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. HOWprototext.Marshalgo MIT-0 · 2026-09-02
• google.golang.org/protobuf v1.36.11: prototext.Unmarshal 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. HOWprototext.Unmarshalgo MIT-0 · 2026-09-02
• google.golang.org/protobuf v1.36.11: protojson.Unmarshal 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. HOWprotojson.Unmarshal MIT-0 · 2026-09-02