Recordsgolanggoogle.golang.org/genproto/googleapis/api
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
The cube reads the newest 6 versions and the first 10 symbols of each, so an empty cell here can mean "outside that window" rather than "never measured".
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-20250728155136-f173205681a0
linux · go@1.26
2 FAIL
· stage: PROJECT_RESOLVE
· fingerprint: sha256:e59175c98b5c0fa609edd5fd409c478db2388a0ff3fd37f555665e61201129b7
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| google.golang.org/genproto/googleapis/rpc | v0.0.0-20250721164621-a45f3dfb1074 | CANDIDATE Correlated change; unproven combination | nothing measured | 1 project-day |
| google.golang.org/genproto/googleapis/rpc | v0.0.0-20250728155136-f173205681a0 | CANDIDATE Correlated change; unproven combination | contract passed | 8 project-days |
| google.golang.org/grpc | v1.71.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| google.golang.org/grpc | v1.75.1 | CANDIDATE Correlated change; unproven combination | contract passed | 8 project-days |
| google.golang.org/protobuf | v1.36.10 | CANDIDATE Correlated change; unproven combination | contract passed | 8 project-days |
| google.golang.org/protobuf | v1.36.6 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
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-20260825221802-da73d73af1c5 | v0.0.0-20260819154853-08b0e4226688 | v0.0.0-20260406210006-6f92a3bedf2d | v0.0.0-20260401024825-9d38bb4040a9 | v0.0.0-20250728155136-f173205681a0 | v0.0.0-20250218202821-56aae31c358a | v0.0.0-20241007155032-5fefd90f89a9 | v0.0.0-20240826202546-f6391c0de4c7 | v0.0.0-20240401170217-c3f982113cda |
|---|---|---|---|---|---|---|---|---|---|
| google.golang.org/genproto/googleapis/rpc | v0.0.0-20260825221802-da73d73af1c5 | v0.0.0-20260819154853-08b0e4226688 | v0.0.0-20260427160629-7cedc36a6bc4 | v0.0.0-20260401024825-9d38bb4040a9 | v0.0.0-20250721164621-a45f3dfb1074 | v0.0.0-20250218202821-56aae31c358a | v0.0.0-20241007155032-5fefd90f89a9 | v0.0.0-20240826202546-f6391c0de4c7 | — |
| google.golang.org/grpc | v1.83.2 | v1.83.1 | v1.81.0 | v1.80.0 | v1.71.0 | v1.71.0 | v1.67.1 | v1.65.0 | v1.63.2 |
| google.golang.org/protobuf | v1.36.12 | v1.36.12 | v1.36.11 | v1.36.11 | v1.36.6 | v1.36.5 | v1.35.1 | v1.34.2 | v1.33.0 |
Moved: 3 · 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.