Recordsgolanggoogle.golang.org/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.14.0
linux · go@1.26
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9eae388b4d8879874dfb354cd6535aed054511b6a410d64f40d8bc6c5e7956a8
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/google/go-cmp | v0.3.0 | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| github.com/googleapis/gax-go/v2 | v2.0.5 | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| golang.org/x/lint | v0.0.0-20190930215403-16217165b5de | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| golang.org/x/oauth2 | v0.0.0-20190604053449-0f29369cfe45 | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| golang.org/x/sync | v0.0.0-20190423024810-112230192c58 | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| golang.org/x/sys | v0.0.0-20190624142023-c5567b49c5d0 | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| golang.org/x/tools | v0.0.0-20191115202509-3a792d9c32b2 | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| google.golang.org/appengine | v1.6.1 | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| google.golang.org/genproto | v0.0.0-20191115194625-c23dd37a84c9 | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| google.golang.org/grpc | v1.21.1 | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| honnef.co/go/tools | v0.0.1-2019.2.3 | CANDIDATE Correlated change; unproven combination | contract passed | 5 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: 24 · 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.