Recordsgolanggo.uber.org/multierrv1.5.0multierr.AppendInto
Change the conditions
Current conditions
multierr.AppendInto @v1.5.0debian 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
- 2 / 2
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-17
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 4. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/stretchr/testify | v1.3.0 | CHANGED Version changed, no linked failure | contract passed | 1 project-day |
| github.com/stretchr/testify | v1.7.0 | CHANGED Version changed, no linked failure | contract passed | 6 project-days |
| github.com/stretchr/testify | v1.8.1 | CHANGED Version changed, no linked failure | contract passed | 10 project-days |
| go.uber.org/atomic | v1.6.0 | CHANGED Version changed, no linked failure | contract passed | 17 project-days |
| go.uber.org/tools | v0.0.0-20190618225709-2cfd321de3ee | PASS All observations passed | contract passed | 17 project-days |
| golang.org/x/lint | v0.0.0-20190930215403-16217165b5de | PASS All observations passed | contract passed | 17 project-days |
| honnef.co/go/tools | v0.0.1-2019.2.3 | PASS All observations passed | contract passed | 17 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: 2 · unchanged at every release: 3
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.