Recordsgolanggolang.org/x/textv0.40.0
Change the conditions
Current conditions
golang.org/x/text @v0.40.0ubuntu glibc · x64 · go 1.26 · go 1
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
- 2 / 4
- Contract verifications
- 0 / 1
- Usage records
- 3
- Independent reporting peers
- 1
- Last recorded
- 2026-09-02
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.40.0 golang.org/x/tools@v0.47.0
linux · go@1.26
1 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:bed685930873883c4ef3e80f9aa41f1a7c1e3a2c11579d314102313e7bd6ebf5
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| golang.org/x/tools | v0.47.0 | FAIL Linked failure observed; version changed across releases | builds observed | 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.
| Library | v0.41.0 | v0.40.0 | v0.37.0 | v0.36.0 | v0.35.0 | v0.34.0 | v0.23.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.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.
Recent failure clusters
-
observed PROJECT_COMPILE exit 1 ×1 v0.40.0 os=linux · runtime=go@1.26 sha256:bed685930873…<path> undefined: config.RoundTripperFromConfig · <path> undefined: config.RoundTripperFromConfiggo/compiler · compiler-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-30
-
observed PROJECT_TEST exit 1 ×1 v0.40.0 os=linux · runtime=go@1.26 sha256:93a9cf8f2e92…--- FAIL: TestSecretSerializationMasking (0.00s) · FAIL example.com/csx-prometheus-common-config-test 0.012sgo/test · test-runner-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-30
-
observed UNKNOWN exit 1 Evidence gap ×1 v0.40.0 os=linux · runtime=go@1.26 sha256:44a92da7386c…# example.com/tlsutil-sample/test · test/contract.go:<n>:<n>: not enough return values · have (*tls.Certificate, error) …go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-02 · Last seen: 2026-09-02Diagnostic re-verification candidate