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
Dependency changes observed: 9. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/cncf/xds/go | v0.0.0-20240723142845-024c85f92f20 | CHANGED Version changed, no linked failure | contract passed | 13 project-days |
| github.com/envoyproxy/protoc-gen-validate | v1.1.0 | CHANGED Version changed, no linked failure | builds observed | 13 project-days |
| github.com/prometheus/client_model | v0.6.0 | CHANGED Version changed, no linked failure | nothing measured | 13 project-days |
| go.opentelemetry.io/proto/otlp | v1.0.0 | CHANGED Version changed, no linked failure | nothing measured | 13 project-days |
| google.golang.org/genproto/googleapis/api | v0.0.0-20240814211410-ddb44dafa142 | CHANGED Version changed, no linked failure | nothing measured | 13 project-days |
| google.golang.org/genproto/googleapis/rpc | v0.0.0-20240814211410-ddb44dafa142 | CHANGED Version changed, no linked failure | builds observed | 13 project-days |
| google.golang.org/grpc | v1.67.1 | CHANGED Version changed, no linked failure | contract passed | 13 project-days |
| google.golang.org/protobuf | v1.35.2 | CHANGED Version changed, no linked failure | contract passed | 12 project-days |
| google.golang.org/protobuf | v1.36.11 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| github.com/planetscale/vtprotobuf | v0.6.1-0.20240319094008-0393e58bdf10 | PASS All observations passed | contract passed | 13 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.