Recordsgolanggithub.com/cncf/xds/go
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
v0.0.0-20251110193048-8bfbf64dc13e
linux · go@1.26
1 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:4b2b0e15a2f05affcf6c094626a7238844f891e10f924b91c6645e069ae831d7
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| cel.dev/expr | v0.24.0 | CANDIDATE Correlated change; unproven combination | contract passed | 32 project-days |
| github.com/envoyproxy/protoc-gen-validate | v1.2.1 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| github.com/envoyproxy/protoc-gen-validate | v1.3.0 | CANDIDATE Correlated change; unproven combination | builds observed | 31 project-days |
| google.golang.org/genproto/googleapis/api | v0.0.0-20240903143218-8af14fe29dc1 | CANDIDATE Correlated change; unproven combination | nothing measured | 1 project-day |
| google.golang.org/genproto/googleapis/api | v0.0.0-20251029180050-ab9386a59fda | CANDIDATE Correlated change; unproven combination | contract passed | 31 project-days |
| google.golang.org/grpc | v1.68.0 | CANDIDATE Correlated change; unproven combination | nothing measured | 1 project-day |
| google.golang.org/grpc | v1.78.0 | CANDIDATE Correlated change; unproven combination | contract passed | 31 project-days |
| google.golang.org/protobuf | v1.36.10 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| google.golang.org/protobuf | v1.36.11 | CANDIDATE Correlated change; unproven combination | contract passed | 31 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.
| Library | v0.0.0-20260202195803-dba9d589def2 | v0.0.0-20251210132809-ee656c7534f5 | v0.0.0-20251110193048-8bfbf64dc13e | v0.0.0-20250501225837-2ac532fd4443 | v0.0.0-20240723142845-024c85f92f20 |
|---|---|---|---|---|---|
| cel.dev/expr | v0.25.2 | v0.25.1 | v0.24.0 | v0.15.0 | v0.15.0 |
| github.com/envoyproxy/protoc-gen-validate | v1.3.0 | v1.3.0 | v1.2.1 | v1.3.0 | v1.0.4 |
| google.golang.org/genproto/googleapis/api | v0.0.0-20260706201446-f0a921348800 | v0.0.0-20260316180232-0b37fe3546d5 | v0.0.0-20240903143218-8af14fe29dc1 | v0.0.0-20230822172742-b8732ec3820d | v0.0.0-20230822172742-b8732ec3820d |
| google.golang.org/grpc | v1.84.0 | v1.79.2 | v1.68.0 | v1.59.0 | v1.59.0 |
| google.golang.org/protobuf | v1.36.10 | v1.36.11 | v1.36.10 | v1.36.12 | v1.36.11 |
Moved: 5 · 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.