Recordsgolangcloud.google.com/go
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
Dependency changes observed: 27. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| cloud.google.com/go/storage | v1.10.0 | CHANGED Version changed, no linked failure | contract passed | 5 project-days |
| github.com/golang/mock | v1.4.4 | CHANGED Version changed, no linked failure | contract passed | 5 project-days |
| github.com/golang/protobuf | v1.4.2 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| github.com/golang/protobuf | v1.5.0 | CHANGED Version changed, no linked failure | contract passed | 2 project-days |
| github.com/golang/protobuf | v1.5.2 | CHANGED Version changed, no linked failure | contract passed | 2 project-days |
| github.com/google/go-cmp | v0.5.1 | CHANGED Version changed, no linked failure | builds observed | 1 project-day |
| github.com/google/go-cmp | v0.5.5 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| github.com/google/go-cmp | v0.7.0 | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| github.com/google/martian/v3 | v3.0.0 | CHANGED Version changed, no linked failure | contract passed | 5 project-days |
| github.com/google/pprof | v0.0.0-20200708004538-1a94d8640e99 | CHANGED Version changed, no linked failure | contract passed | 5 project-days |
| github.com/googleapis/gax-go/v2 | v2.0.5 | CHANGED Version changed, no linked failure | contract passed | 5 project-days |
| github.com/jstemmer/go-junit-report | v0.9.1 | CHANGED Version changed, no linked failure | contract passed | 5 project-days |
| golang.org/x/lint | v0.0.0-20200302205851-738671d3881b | CHANGED Version changed, no linked failure | contract passed | 5 project-days |
| golang.org/x/net | v0.0.0-20200822124328-c89045814202 | CHANGED Version changed, no linked failure | builds observed | 1 project-day |
| golang.org/x/net | v0.0.0-20210525063256-abc453219eb5 | CHANGED Version changed, no linked failure | builds observed | 3 project-days |
| golang.org/x/net | v0.4.0 | CHANGED Version changed, no linked failure | builds observed | 1 project-day |
| golang.org/x/oauth2 | v0.0.0-20200107190931-bf48bf16ab8d | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| golang.org/x/oauth2 | v0.0.0-20210514164344-f6687ab2804c | CHANGED Version changed, no linked failure | builds observed | 3 project-days |
| golang.org/x/oauth2 | v0.0.0-20220223155221-ee480838109b | CHANGED Version changed, no linked failure | builds observed | 1 project-day |
| golang.org/x/text | v0.3.3 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| golang.org/x/text | v0.3.6 | CHANGED Version changed, no linked failure | contract passed | 3 project-days |
| golang.org/x/text | v0.5.0 | CHANGED Version changed, no linked failure | builds observed | 1 project-day |
| golang.org/x/tools | v0.0.0-20200825202427-b303f430e36d | CHANGED Version changed, no linked failure | builds observed | 2 project-days |
| golang.org/x/tools | v0.1.12 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| google.golang.org/api | v0.30.0 | CHANGED Version changed, no linked failure | contract passed | 5 project-days |
| google.golang.org/genproto | v0.0.0-20200825200019-8632dd797987 | CHANGED Version changed, no linked failure | builds observed | 5 project-days |
| google.golang.org/grpc | v1.31.0 | CHANGED Version changed, no linked failure | builds observed | 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: 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.