CodeSampleX

Recordsgolanggo.opentelemetry.io/auto/sdkv1.1.0go.opentelemetry.io/auto/sdk.TracerProvider

Change the conditions
Fixed
OSalpine musl Symbolgo.opentelemetry.io/auto/sdk.TracerProvider
Filter Runtimego 1.26 Package versionv1.1.0 Architecturex64 Package managergo Execution contextgo libcmusl Clear filters

Current conditions

go.opentelemetry.io/auto/sdk.TracerProvider @v1.1.0alpine musl · 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 (3)

Project observations
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-08-27
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 8 · Steady 0

First observed break

v1.1.0

go@1.26

19 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
github.com/stretchr/testify v1.10.0 CANDIDATE Correlated change; unproven combination builds observed 40 project-days
github.com/stretchr/testify v1.11.1 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
go.opentelemetry.io/otel v1.34.0 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
go.opentelemetry.io/otel v1.35.0 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
go.opentelemetry.io/otel v1.37.0 CANDIDATE Correlated change; unproven combination contract passed 44 project-days
go.opentelemetry.io/otel/trace v1.34.0 CANDIDATE Correlated change; unproven combination builds observed 3 project-days
go.opentelemetry.io/otel/trace v1.35.0 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
go.opentelemetry.io/otel/trace v1.37.0 CANDIDATE Correlated change; unproven combination contract passed 44 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.

Libraryv1.2.1v1.1.0
github.com/stretchr/testify v1.12.1 v1.11.1
go.opentelemetry.io/otel v1.44.0 v1.34.0
go.opentelemetry.io/otel/trace v1.44.0 v1.34.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