Recordsgolanggithub.com/stretchr/testifyv1.10.0
Change the conditions
Current conditions
github.com/stretchr/testify @v1.10.0debian glibc · x64 · go 1.26 · go · go
package-level total, not an API
Recorded as present in projects. Nothing was run at this coordinate.
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- nothing at this coordinate
- Contract verifications
- nothing at this coordinate
- Usage records
- 7
- Independent reporting peers
- 2
- Last recorded
- 2026-09-17
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.10.0
linux · go@1.26
1 FAIL
· stage: PROJECT_TEST
· fingerprint: sha256:943c460a4a7e8c85f76c1aa6a5c18d93f62bf3cfeed5fe56730287702c24d8c5
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/davecgh/go-spew | v1.1.1 | CANDIDATE Correlated change; unproven combination | contract passed | 69 project-days |
| github.com/pmezard/go-difflib | v1.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 69 project-days |
| gopkg.in/yaml.v3 | v3.0.1 | CANDIDATE Correlated change; unproven combination | contract passed | 69 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 | v1.12.1 | v1.11.1 | v1.10.0 | v1.9.0 | v1.8.4 | v1.8.1 | v1.8.0 | v1.7.5 | v1.7.1 | v1.7.0 | v1.6.1 | v1.5.1 | v1.4.0 | v1.3.0 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| github.com/davecgh/go-spew | — | v1.1.2-0.20180830191138-d8f796af33cc | v1.1.1 | v1.1.1 | v1.1.1 | v1.1.1 | v1.1.1 | v1.1.1 | v1.1.1 | v1.1.0 | v1.1.1 | v1.1.1 | v1.1.0 | v1.1.0 |
| github.com/pmezard/go-difflib | — | v1.0.1-0.20181226105442-5d4384ee4fb2 | v1.0.0 | v1.0.0 | v1.0.0 | v1.0.0 | v1.0.0 | v1.0.0 | v1.0.0 | v1.0.0 | v1.0.0 | v1.0.0 | v1.0.0 | v1.0.0 |
| github.com/stretchr/objx | v0.5.3 | v0.5.2 | — | v0.5.2 | v0.5.3 | v0.2.0 | v0.4.0 | — | — | v0.2.0 | v0.1.0 | v0.1.0 | v0.1.0 | v0.2.0 |
| gopkg.in/yaml.v2 | — | — | — | — | — | — | — | — | — | — | — | v2.3.0 | v2.4.0 | — |
| gopkg.in/yaml.v3 | — | v3.0.1 | v3.0.1 | v3.0.1 | v3.0.1 | v3.0.1 | v3.0.1 | v3.0.1 | v3.0.0-20210107192922-496545a6307b | v3.0.1 | v3.0.0-20200313102051-9f266ea9e77c | — | — | — |
| go.yaml.in/yaml/v3 | v3.0.5 | — | — | — | — | — | — | — | — | — | — | — | — | — |
Moved: 5 · 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 PROJECT_TEST exit 1 ×1 v1.10.0 os=linux · runtime=go@1.26 sha256:943c460a4a7e…--- FAIL: TestErrorHandlerFuncAndNilHandling (0.00s) · === RUN TestConcurrentErrorHandling · --- PASS: TestConcurrentErrorHandling (0.00s) …go/test · test-runner-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29