CodeSampleX

Recordsgolanggo.opentelemetry.io/otelv1.45.0go.opentelemetry.io/otel/sdk/resource.Default

Change the conditions
Fixed
OSlinux Symbolgo.opentelemetry.io/otel/sdk/resource.Default
Filter Runtimego 1.26 Package versionv1.45.0 Architecturex64 Package managergomod Execution contextgo libcmusl Clear filters

Current conditions

go.opentelemetry.io/otel/sdk/resource.Default @v1.45.0linux · musl · x64 · go 1.26 · gomod · go

1 of 2 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and this coordinate records both a passing and a failing run of it (1)

Project observations
nothing at this coordinate
Contract verifications
1 / 2
Cross-checked
reproduced by two or more independent peers
Last recorded
2026-09-07
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 6 · Steady 2

First observed break

v1.45.0

go@1.26

5 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
github.com/go-logr/logr v1.4.4 CANDIDATE Correlated change; unproven combination contract passed 23 project-days
github.com/google/go-cmp v0.7.0 CANDIDATE Correlated change; unproven combination contract passed 23 project-days
github.com/stretchr/testify v1.11.1 CANDIDATE Correlated change; unproven combination contract passed 23 project-days
go.opentelemetry.io/auto/sdk v1.2.1 CANDIDATE Correlated change; unproven combination contract passed 23 project-days
go.opentelemetry.io/otel/metric v1.45.0 CANDIDATE Correlated change; unproven combination builds observed 23 project-days
go.opentelemetry.io/otel/trace v1.45.0 CANDIDATE Correlated change; unproven combination contract passed 23 project-days
github.com/cespare/xxhash/v2 v2.3.0 PASS All observations passed contract passed 23 project-days
github.com/go-logr/stdr v1.2.2 PASS All observations passed contract passed 23 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.46.0v1.45.0v1.44.0v1.43.0v1.37.0v1.35.0v1.34.0v1.28.0v1.24.0
github.com/go-logr/logr v1.4.4 v1.4.4 v1.4.3 v1.4.4 v1.4.3 v1.4.2 v1.4.2 v1.4.2 v1.4.1
github.com/google/go-cmp v0.7.0 v0.7.0 v0.7.0 v0.7.0 v0.7.0 v0.7.0 v0.6.0 — v0.6.0
github.com/stretchr/testify v1.12.1 v1.11.1 v1.11.1 v1.11.1 v1.11.1 v1.10.0 — — v1.8.4
go.opentelemetry.io/auto/sdk v1.2.1 v1.2.1 v1.2.1 v1.2.1 v1.1.0 v1.1.0 v1.1.0 — —
go.opentelemetry.io/otel/metric v1.46.0 v1.45.0 v1.44.0 v1.43.0 v1.37.0 v1.35.0 v1.34.0 v1.28.0 v1.24.0
go.opentelemetry.io/otel/trace v1.46.0 v1.45.0 v1.44.0 v1.43.0 v1.37.0 v1.35.0 v1.34.0 v1.28.0 v1.24.0
github.com/cespare/xxhash/v2 v2.3.0 v2.3.0 v2.3.0 v2.3.0 — — — — —
github.com/go-logr/stdr v1.2.2 v1.2.2 v1.2.2 v1.2.2 v1.2.2 v1.2.2 v1.2.2 v1.2.2 v1.2.2

Moved: 6 · unchanged at every release: 2

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