CodeSampleX

Recordsgolanggo.uber.org/multierrv1.10.0multierr.AppendFunc

Change the conditions
Fixed
Package versionv1.10.0 Symbolmultierr.AppendFunc
Filter OSalpine musl Runtimego 1.26 Architecturex64 Package managergo Execution contextgo libcmusl Clear filters

Current conditions

multierr.AppendFunc @v1.10.0alpine musl · 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 (2)

Project observations
nothing at this coordinate
Contract verifications
2 / 2
Last recorded
2026-08-27

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

v1.10.0

go@1.26

3 FAIL · stage: PROJECT_TEST

Library Version Health Measured there Projects
github.com/stretchr/testify v1.8.1 CANDIDATE Correlated change; unproven combination contract passed 20 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.

Recent failure clusters