CodeSampleX

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.

Fixed
OSdebian glibc
Filter Runtimego 1.26 Architecturex64 Package managergo Execution contextgo libcglibc Clear filters
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

Observed problems 1 · Changed 3 · Steady 0

First observed break

v0.0.0-20260401024825-9d38bb4040a9

linux

16 FAIL · stage: PROCESS_START · fingerprint: sha256:c12549970456efb5abdc90b679695c6689107d4f097d612245d6bfb25e01ec32

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.

Libraryv0.0.0-20260825221802-da73d73af1c5v0.0.0-20260819154853-08b0e4226688v0.0.0-20260406210006-6f92a3bedf2dv0.0.0-20260401024825-9d38bb4040a9v0.0.0-20250728155136-f173205681a0v0.0.0-20250218202821-56aae31c358av0.0.0-20241007155032-5fefd90f89a9v0.0.0-20240826202546-f6391c0de4c7v0.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.