Recordsgolangcloud.google.com/go
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
First observed break
v0.37.0
linux · go@1.26
4 FAIL
· stage: UNKNOWN
· fingerprint: sha256:3b3190f2cd44c327e0d62d5fcac6e314a022dc126a98b5c1b38661e44ab6a020
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/golang/mock | v1.2.0 | CANDIDATE Correlated change; unproven combination | nothing measured | 7 project-days |
| github.com/golang/protobuf | v1.2.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| github.com/golang/protobuf | v1.3.1 | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| github.com/golang/protobuf | v1.5.4 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| github.com/google/go-cmp | v0.2.0 | CANDIDATE Correlated change; unproven combination | nothing measured | 6 project-days |
| github.com/google/go-cmp | v0.6.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| github.com/google/pprof | v0.0.0-20181206194817-3ea8567a2e57 | CANDIDATE Correlated change; unproven combination | nothing measured | 6 project-days |
| github.com/google/pprof | v0.0.0-20231212022811-ec68065c825e | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| github.com/googleapis/gax-go/v2 | v2.0.3 | CANDIDATE Correlated change; unproven combination | builds observed | 7 project-days |
| github.com/jstemmer/go-junit-report | v0.0.0-20190106144839-af01ea7f8024 | CANDIDATE Correlated change; unproven combination | contract passed | 7 project-days |
| golang.org/x/lint | v0.0.0-20190227174305-5b3e6a55c961 | CANDIDATE Correlated change; unproven combination | contract passed | 7 project-days |
| golang.org/x/oauth2 | v0.0.0-20181203162652-d668ce993890 | CANDIDATE Correlated change; unproven combination | nothing measured | 1 project-day |
| golang.org/x/oauth2 | v0.0.0-20190226205417-e64efc72b421 | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| golang.org/x/oauth2 | v0.16.0 | CANDIDATE Correlated change; unproven combination | nothing measured | 1 project-day |
| golang.org/x/text | v0.23.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| golang.org/x/text | v0.3.1-0.20180807135948-17ff2d5776d2 | CANDIDATE Correlated change; unproven combination | nothing measured | 6 project-days |
| golang.org/x/tools | v0.0.0-20190226205152-f727befe758c | CANDIDATE Correlated change; unproven combination | contract passed | 6 project-days |
| golang.org/x/tools | v0.31.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| google.golang.org/api | v0.1.0 | CANDIDATE Correlated change; unproven combination | contract passed | 7 project-days |
| google.golang.org/genproto | v0.0.0-20190306203927-b5d61aea6440 | CANDIDATE Correlated change; unproven combination | contract passed | 7 project-days |
| google.golang.org/grpc | v1.19.0 | CANDIDATE Correlated change; unproven combination | contract passed | 6 project-days |
| google.golang.org/grpc | v1.67.1 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| honnef.co/go/tools | v0.0.0-20190106161140-3f1c8253044a | CANDIDATE Correlated change; unproven combination | contract passed | 6 project-days |
| github.com/google/btree | v0.0.0-20180813153112-4030bb1f1f0c | UNKNOWN No linked outcome measured | nothing measured | 7 project-days |
| github.com/google/martian | v2.1.0+incompatible | UNKNOWN No linked outcome measured | nothing measured | 7 project-days |
| golang.org/x/sync | v0.0.0-20190227155943-e225da77a7e6 | UNKNOWN No linked outcome measured | nothing measured | 6 project-days |
| golang.org/x/time | v0.0.0-20181108054448-85acf8d2951c | UNKNOWN No linked outcome measured | nothing measured | 6 project-days |
| golang.org/x/build | v0.0.0-20190111050920-041ab4dc3f9d | PASS All observations passed | contract passed | 7 project-days |
| golang.org/x/sync | v0.12.0 | PASS All observations passed | contract passed | 1 project-day |
| golang.org/x/time | v0.11.0 | PASS All observations passed | 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.
Moved: 19 · unchanged at every release: 11
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.