Records/golang/github.com/envoyproxy/go-control-plane/envoy/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.39.0 PASS 1 passing observations
• v1.37.0 PASS 1 passing observations
• v1.36.0 not measured
• v1.32.2 FAIL

Where it reproduced

• os=linux · runtime=go@1.26 ×1 2026-10-16 → 2026-10-16

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 failing release v1.32.2 → first passing release v1.37.0

  Releases between them never measured at this stage: 1

  What differs across the boundary

  • github.com/cncf/xds/go v0.0.0-20251110193048-8bfbf64dc13e, v0.0.0-20260202195803-dba9d589def2 → v0.0.0-20240723142845-024c85f92f20 hypothesis
  • github.com/envoyproxy/go-control-plane v0.14.0 → — hypothesis
  • github.com/envoyproxy/protoc-gen-validate v1.3.0, v1.3.3 → v1.1.0 hypothesis
  • github.com/prometheus/client_model v0.6.2 → v0.6.0 hypothesis
  • go.opentelemetry.io/proto/otlp v1.9.0 → v1.0.0 hypothesis
  • google.golang.org/genproto/googleapis/api v0.0.0-20251029180050-ab9386a59fda, v0.0.0-20260414002931-afd174a4e478, v0.0.0-20260630182238-925bb5da69e7, v0.0.0-20260706201446-f0a921348800 → v0.0.0-20240814211410-ddb44dafa142 hypothesis
  • google.golang.org/genproto/googleapis/rpc v0.0.0-20251029180050-ab9386a59fda, v0.0.0-20260630182238-925bb5da69e7, v0.0.0-20260807164820-c8921c73eeea → v0.0.0-20240814211410-ddb44dafa142 hypothesis
  • google.golang.org/grpc v1.78.0, v1.82.0, v1.83.2, v1.84.0 → v1.67.1 hypothesis
  • google.golang.org/protobuf v1.36.11, v1.36.12 → v1.35.2, 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: 8 · unchanged at every release: 2

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: 1
• No failure domain was inferred for this failure.

Published answers for the affected releases

• github.com/envoyproxy/go-control-plane/envoy v1.32.2: v3.Cluster_LbPolicy 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. HOWgithub.com/envoyproxy/go-control-plane/envoy/config/cluster/v3.Cluster_LbPolicy MIT-0 · 2026-10-16
• github.com/envoyproxy/go-control-plane/envoy v1.32.2: v3.Cluster_DnsLookupFamily_value 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. HOWgithub.com/envoyproxy/go-control-plane/envoy/config/cluster/v3.Cluster_DnsLookupFamily_value MIT-0 · 2026-10-16
• github.com/envoyproxy/go-control-plane/envoy v1.32.2: v3.Cluster_CLUSTER_PROVIDED 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. HOWgithub.com/envoyproxy/go-control-plane/envoy/config/cluster/v3.Cluster_CLUSTER_PROVIDED MIT-0 · 2026-10-16