Recordsgolanggolang.org/x/textv0.16.0golang.org/x/text/cases.Caser
Change the conditions
Current conditions
golang.org/x/text/cases.Caser @v0.16.0debian glibc · x64 · go 1.26 · go · go
1 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 came back clean (1)
- Project observations
- 2 / 2
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-17
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.16.0
linux · go@1.26
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:b6c3d897dc6085789b9d015d8219efb35e4f9139741d5f0c659ad6500f484f3a
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/tools | v0.2.0 | CANDIDATE Correlated change; unproven combination | nothing measured | 1 project-day |
| golang.org/x/tools | v0.21.1-0.20240508182429-e35e4ccd0d2d | CANDIDATE Correlated change; unproven combination | nothing measured | 10 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.37.0 | v0.36.0 | v0.35.0 | v0.34.0 | v0.29.0 | v0.28.0 | v0.27.0 | v0.26.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.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.44.0 | v0.43.0 | v0.42.0 | v0.41.0 | v0.36.0 | v0.35.0 | v0.34.0 | v0.33.0 | 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.6.0 | v0.6.0 | v0.6.0 | v0.1.12 | v0.1.12 | v0.0.0-20200825202427-b303f430e36d | v0.0.0-20200825202427-b303f430e36d | v0.0.0-20200331025713-a30bf2db82d4 |
| 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 ×1 v0.16.0 os=linux · runtime=go@1.26 sha256:b6c3d897dc60…Contract test failed: expected English tag for BritishEnglish match, got en-u-rg-gbzzzz · exit status 1go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-15 · Last seen: 2026-09-15Diagnostic re-verification candidate