Recordsgolanggolang.org/x/text
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
v0.22.0 golang.org/x/tools@v0.21.1-0.20240508182429-e35e4ccd0d2d
linux · go@1.26
1 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:e84876b56a4ec8e1f48de316c59e37f88c5c83ef59ca283b87b295afc6210204
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/tools | v0.21.1-0.20240508182429-e35e4ccd0d2d | FAIL Linked failure observed; version changed across releases | nothing measured | 7 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.
| Library | v0.41.0 | v0.40.0 | v0.37.0 | v0.36.0 | v0.35.0 | v0.34.0 | v0.22.0 | v0.21.0 | v0.14.0 | v0.5.0 | v0.3.6 | v0.3.3 | v0.3.2 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| golang.org/x/tools | v0.48.0 | v0.47.0 | v0.44.0 | v0.44.0 | v0.42.0 | v0.41.0 | v0.21.1-0.20240508182429-e35e4ccd0d2d | v0.21.1-0.20240508182429-e35e4ccd0d2d | v0.6.0 | v0.1.12 | v0.0.0-20200825202427-b303f430e36d | v0.0.0-20180917221912-90fa682c2a6e | v0.0.0-20180917221912-90fa682c2a6e |
| golang.org/x/mod | — | — | — | — | — | — | — | — | — | v0.6.0-dev.0.20220419223038-86c51ed26bb4 | — | — | — |
| golang.org/x/sys | — | — | — | — | — | — | — | — | — | v0.47.0 | — | — | — |
Moved: 1 · unchanged at every release: 2
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.