Recordsgolanggithub.com/stretchr/testifyv1.11.1assert.Equal
Change the conditions
Current conditions
assert.Equal @v1.11.1alpine musl · x64 · go 1.26 · gomod · 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-18
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| github.com/davecgh/go-spew | v1.1.1 | contract passed | 30 project-days |
| github.com/pmezard/go-difflib | v1.0.0 | contract passed | 30 project-days |
| github.com/stretchr/objx | v0.1.0 | nothing measured | 1 project-day |
| gopkg.in/yaml.v3 | v3.0.1 | contract passed | 30 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.11.1 | v1.8.1 | v1.4.0 |
|---|---|---|---|
| github.com/davecgh/go-spew | v1.1.1 | v1.1.1 | v1.1.1 |
| github.com/pmezard/go-difflib | v1.0.0 | v1.0.0 | v1.0.0 |
| github.com/stretchr/objx | v0.1.0 | — | — |
| gopkg.in/yaml.v3 | v3.0.1 | v3.0.1 | — |
Moved: 0 · unchanged at every release: 4
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.