Recordsgolanggithub.com/envoyproxy/go-control-plane/envoy
there is a sample for this release and API (1)
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
How to read the grid
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Cells are aggregates of everything still varying in this slice (the n/m count says how much). Click one to pin its coordinates and see the next level.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.39.0
linux · go@1.26
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:0882784d80c20e919569b4a9a1a5ff54eb0aa7665750aedc7afd0bce723472f8
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/cncf/xds/go | v0.0.0-20260202195803-dba9d589def2 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| github.com/envoyproxy/protoc-gen-validate | v1.3.3 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| github.com/prometheus/client_model | v0.6.2 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| go.opentelemetry.io/proto/otlp | v1.10.0 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| google.golang.org/genproto/googleapis/api | v0.0.0-20260414002931-afd174a4e478 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| google.golang.org/genproto/googleapis/rpc | v0.0.0-20260414002931-afd174a4e478 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| google.golang.org/grpc | v1.82.0 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| google.golang.org/protobuf | v1.36.11 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| google.golang.org/protobuf | v1.36.12 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| github.com/envoyproxy/go-control-plane | v0.14.0 | PASS All observations passed | contract passed | 4 project-days |
| github.com/planetscale/vtprotobuf | v0.6.1-0.20240319094008-0393e58bdf10 | PASS All observations passed | contract passed | 4 project-days |
The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.
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.