Recordsgolanggoogle.golang.org/appengine
no sample at this coordinate yet
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
v1.4.0
linux · go@1.26
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:0cc5633d6f9aa11fdb97a30243cae2d23c42f9bbcc21f59ae64b43eea06d4a3e
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/golang/protobuf | v1.2.0 | CANDIDATE Correlated change; unproven combination | contract passed | 10 project-days |
| github.com/golang/protobuf | v1.3.1 | CANDIDATE Correlated change; unproven combination | contract passed | 13 project-days |
| github.com/golang/protobuf | v1.3.2 | CANDIDATE Correlated change; unproven combination | contract passed | 30 project-days |
| github.com/golang/protobuf | v1.3.3 | CANDIDATE Correlated change; unproven combination | contract passed | 20 project-days |
| github.com/golang/protobuf | v1.4.1 | CANDIDATE Correlated change; unproven combination | contract passed | 27 project-days |
| github.com/golang/protobuf | v1.4.2 | CANDIDATE Correlated change; unproven combination | contract passed | 37 project-days |
| github.com/golang/protobuf | v1.4.3 | CANDIDATE Correlated change; unproven combination | contract passed | 22 project-days |
| github.com/golang/protobuf | v1.5.2 | CANDIDATE Correlated change; unproven combination | contract passed | 12 project-days |
| github.com/golang/protobuf | v1.5.4 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| golang.org/x/net | v0.0.0-20190213061140-3a22650c66bd | CANDIDATE Correlated change; unproven combination | nothing measured | 10 project-days |
| golang.org/x/net | v0.0.0-20190311183353-d8887717615a | CANDIDATE Correlated change; unproven combination | contract passed | 115 project-days |
| golang.org/x/net | v0.0.0-20190313220215-9f648a60d977 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| golang.org/x/net | v0.0.0-20190603091049-60506f45cf65 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| golang.org/x/net | v0.0.0-20190628185345-da137c7871d7 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| golang.org/x/net | v0.0.0-20200625001655-4c5254603344 | CANDIDATE Correlated change; unproven combination | contract passed | 16 project-days |
| golang.org/x/net | v0.0.0-20200822124328-c89045814202 | CANDIDATE Correlated change; unproven combination | contract passed | 16 project-days |
| golang.org/x/net | v0.0.0-20210405180319-a5a99cb37ef4 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| golang.org/x/net | v0.55.0 | CANDIDATE Correlated change; unproven combination | contract passed | 1 project-day |
| golang.org/x/text | v0.3.0 | CANDIDATE Correlated change; unproven combination | contract passed | 150 project-days |
| golang.org/x/text | v0.3.1-0.20180807135948-17ff2d5776d2 | CANDIDATE Correlated change; unproven combination | nothing measured | 3 project-days |
| golang.org/x/text | v0.3.2 | CANDIDATE Correlated change; unproven combination | contract passed | 11 project-days |
| golang.org/x/text | v0.3.5 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| golang.org/x/text | v0.37.0 | CANDIDATE Correlated change; unproven combination | 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: 3 · 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.