Recordsgolanggo.uber.org/mock
Change the conditions
Current conditions
gomock.InOrder @v0.5.0linux · x64 · go 1.26 · go · go
2 of 2 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
- 2 / 2
- Independent reporting peers
- 1
- Last recorded
- 2026-09-07
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
debian glibc · x64 · go 1.26 · go · go
1 of 1 passed
Verified — this network ran a contract at this coordinate.
-
alpine musl · x64 · go 1.26 · go · go
1 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.6.0
linux · go@1.26
2 FAIL
· stage: PROJECT_RESOLVE
· fingerprint: sha256:ef468617c7e63453868e004f3489e109835732c4441883f0f9116d85a130eba7
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.