Recordsgolanggo.uber.org/mockv0.5.2go.uber.org/mock/gomock.Matcher
Change the conditions
Current conditions
go.uber.org/mock/gomock.Matcher @v0.5.2linux · 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-17
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.5.2
linux · go@1.26
1 FAIL
· stage: PROJECT_TEST
· fingerprint: sha256:0a9a39bd4766ab4ba0fe89dda5d0cdf0140d9ceed2a8ea0bb2eb7273bbd15791
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/stretchr/testify | v1.11.1 | CANDIDATE Correlated change; unproven combination | contract passed | 10 project-days |
| github.com/stretchr/testify | v1.12.1 | CANDIDATE Correlated change; unproven combination | builds observed | 1 project-day |
| github.com/stretchr/testify | v1.9.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| golang.org/x/mod | v0.18.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 | 11 project-days |
| golang.org/x/tools | v0.22.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| golang.org/x/tools | v0.47.0 | CANDIDATE Correlated change; unproven combination | builds observed | 11 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.6.0 | v0.5.2 | v0.5.0 |
|---|---|---|---|
| github.com/stretchr/testify | v1.11.1 | v1.12.1 | v1.9.0 |
| golang.org/x/mod | v0.35.0 | v0.18.0 | v0.18.0 |
| golang.org/x/tools | v0.44.0 | v0.22.0 | v0.31.0 |
Moved: 3 · unchanged at every release: 0
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 v0.5.2 os=linux · runtime=go@1.26 sha256:0a9a39bd4766…--- FAIL: TestWithContextFatalCancelsContext (0.00s) · panic: runtime error: invalid memory address or nil pointer dereference [recovered, repanicked] …go/test · test-runner-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-05 · Last seen: 2026-09-05