CodeSampleX

Recordsgolanggolang.org/x/expv0.0.0-20251023183803-a4bb9ffd2546golang.org/x/exp/constraints

Change the conditions
Fixed
OSdebian glibc Symbolgolang.org/x/exp/constraints
Filter Runtimego 1.26 Package versionv0.0.0-20251023183803-a4bb9ffd2546 Architecturex64 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

golang.org/x/exp/constraints @v0.0.0-20251023183803-a4bb9ffd2546debian 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
1 / 1
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-09-09

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 8 · Unknown 1 · Steady 0

First observed break

v0.0.0-20251023183803-a4bb9ffd2546

linux · go@1.26

1 FAIL · stage: PROJECT_TEST · fingerprint: sha256:dda800f87ad336ceb3470d5a3d62662cd8dbf7f91f2b28e427be0c6fc592b4b7

Library Version Health Measured there Projects
github.com/google/go-cmp v0.6.0 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
github.com/google/go-cmp v0.7.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
golang.org/x/mod v0.29.0 CANDIDATE Correlated change; unproven combination nothing measured 3 project-days
golang.org/x/mod v0.35.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
golang.org/x/mod v0.37.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
golang.org/x/tools v0.38.0 CANDIDATE Correlated change; unproven combination nothing measured 3 project-days
golang.org/x/tools v0.44.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
golang.org/x/tools v0.46.0 CANDIDATE Correlated change; unproven combination builds observed 2 project-days
golang.org/x/tools/go/packages/packagestest v0.1.1-deprecated UNKNOWN No linked outcome measured nothing measured 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.

Moved: 3 · unchanged at every release: 8

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