CodeSampleX

Recordsgolanggoogle.golang.org/protobuf

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 Package versionv1.32.0
Filter Runtimego 1.26 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 2 · Steady 0

First observed break

v1.32.0

linux · go@1.26

1 FAIL · stage: PROJECT_RESOLVE · fingerprint: sha256:454c17f309fed016123f94a204ad8fc37d70c15e49edd91c650481c720f9678a

Library Version Health Measured there Projects
github.com/golang/protobuf v1.5.0 CANDIDATE Correlated change; unproven combination contract passed 8 project-days
github.com/google/go-cmp v0.5.5 CANDIDATE Correlated change; unproven combination contract passed 8 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.

Libraryv1.36.12v1.36.11v1.36.10v1.36.6v1.36.5v1.35.1v1.34.2v1.33.0v1.32.0v1.31.0v1.28.0v1.26.0v1.26.0-rc.1v1.25.0v1.23.0v1.22.0
github.com/golang/protobuf v1.5.2 v1.5.3 v1.5.4 v1.5.4 v1.5.4 v1.5.4 v1.5.0 v1.5.2 v1.5.0 v1.5.3 v1.5.3 v1.5.3 — v1.4.2 v1.4.3 v1.4.1
github.com/google/go-cmp v0.7.0 v0.7.0 v0.7.0 v0.7.0 v0.6.0 v0.6.0 v0.5.5 v0.6.0 v0.5.5 v0.5.9 v0.6.0 v0.5.5 v0.5.5 v0.5.1 v0.4.0 v0.4.0
google.golang.org/genproto — — — — — — — — — — — — — v0.0.0-20200804131852-c06518451d9c — —

Moved: 2 · unchanged at every release: 1

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.