Recordsgolanggolang.org/x/textv0.36.0
Change the conditions
Current conditions
golang.org/x/text @v0.36.0ubuntu glibc · x64 · node 22 · npm 10 · node
package-level total, not an API
0 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed
- Project observations
- 15 / 15
- Contract verifications
- 0 / 1
- Independent reporting peers
- 2
- Last recorded
- 2026-09-04
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.36.0
go@1.26
6 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:c2ae6d87252c4f443f14d40584c4012a25213fbf0bb7b5e35604e6d35d608229
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/tools | v0.43.0 | CANDIDATE Correlated change; unproven combination | builds observed | 4 project-days |
| golang.org/x/tools | v0.44.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 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.42.0 | v0.41.0 | v0.40.0 | v0.38.0 | v0.37.0 | v0.36.0 | v0.35.0 | v0.34.0 | v0.33.0 | v0.32.0 | v0.31.0 | v0.29.0 | v0.28.0 | v0.27.0 | v0.26.0 | v0.25.0 | v0.24.0 | v0.23.0 | v0.22.0 | v0.21.0 | v0.20.0 | v0.17.0 | v0.16.0 | v0.14.0 | v0.13.0 | v0.12.0 | v0.11.0 | v0.5.0 | v0.4.0 | v0.3.7 | v0.3.6 | v0.3.3 | v0.3.2 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| golang.org/x/sys | — | — | — | — | — | — | — | — | — | — | — | — | — | — | — | — | — | — | — | — | — | — | — | — | — | — | — | v0.47.0 | v0.2.0 | — | — | — | — |
| golang.org/x/tools | v0.49.0 | v0.48.0 | v0.47.0 | v0.45.0 | v0.44.0 | v0.44.0 | v0.42.0 | v0.41.0 | v0.41.0 | v0.39.0 | v0.38.0 | v0.36.0 | v0.35.0 | v0.34.0 | v0.33.0 | v0.21.1-0.20240508182429-e35e4ccd0d2d | v0.21.1-0.20240508182429-e35e4ccd0d2d | v0.31.0 | v0.21.1-0.20240508182429-e35e4ccd0d2d | v0.21.1-0.20240508182429-e35e4ccd0d2d | v0.47.0 | v0.21.1-0.20240508182429-e35e4ccd0d2d | v0.2.0 | v0.6.0 | v0.14.0 | v0.6.0 | v0.6.0 | v0.1.12 | v0.1.12 | v0.1.12 | v0.0.0-20200825202427-b303f430e36d | v0.0.0-20200825202427-b303f430e36d | v0.0.0-20200618134242-20370b0cb4b2 |
| golang.org/x/mod | — | — | — | — | — | — | — | — | — | — | — | — | — | — | — | — | — | — | — | — | — | — | — | — | — | — | — | v0.6.0-dev.0.20220419223038-86c51ed26bb4 | v0.6.0-dev.0.20220419223038-86c51ed26bb4 | — | — | — | — |
Moved: 2 · 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.
Recent failure clusters
-
observed UNKNOWN exit 1 Evidence gap ×5 v0.18.0 → v0.23.0 → v0.29.0 → v0.36.0 os=linux sha256:91ad26545eb1…node:internal/modules/cjs/loader:<n> · throw err; · ^ · Error: Cannot find module <str>node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 2 · First recorded: 2026-08-31 · Last seen: 2026-09-04Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 v0.36.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:0ab3a7004d66…node:assert:<n> · throw new AssertionError(obj); · ^ · AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-04 · Last seen: 2026-09-04Diagnostic re-verification candidate