CodeSampleX

Recordsgolanggolang.org/x/textv0.34.0collate.Collator.CompareString

Change the conditions
Fixed
Symbolcollate.Collator.CompareString libcmusl
Filter OSalpine musl Runtimego 1.26 Package versionv0.34.0 Architecturex64 Package managergo Execution contextgo Clear filters

Current conditions

collate.Collator.CompareString @v0.34.0alpine musl · 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
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-08-26

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 0

First observed break

v0.34.0 golang.org/x/tools@v0.41.0

go@1.26

273 FAIL · stage: PROJECT_TEST

Library Version Health Measured there Projects
golang.org/x/tools v0.41.0 FAIL Linked failure observed; version changed across releases nothing measured 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: 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