CodeSampleX

Recordsgolanggo.opentelemetry.io/otel/sdkv1.34.0go.opentelemetry.io/otel/propagation.TraceContext

Change the conditions
Fixed
Package versionv1.34.0 Symbolgo.opentelemetry.io/otel/propagation.TraceContext
Filter OSalpine musl Runtimego 1.26 Architecturex64 Package managergomod Execution contextgo libcmusl Clear filters

Current conditions

go.opentelemetry.io/otel/propagation.TraceContext @v1.34.0alpine musl · x64 · go 1.26 · gomod · go

0 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 failed (1)

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

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 6 · Steady 1

First observed break

v1.34.0

linux · go@1.26 · executionContext=go

6 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
github.com/go-logr/logr v1.4.2 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
github.com/google/go-cmp v0.6.0 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
go.opentelemetry.io/otel v1.34.0 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
go.opentelemetry.io/otel/trace v1.34.0 CANDIDATE Correlated change; unproven combination builds observed 4 project-days
golang.org/x/sys v0.29.0 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
golang.org/x/sys v0.30.0 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
github.com/google/uuid v1.6.0 PASS All observations passed contract passed 4 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.47.0v1.46.0v1.45.0v1.44.0v1.43.0v1.42.0v1.39.0v1.38.0v1.37.0v1.36.0v1.35.0v1.34.0v1.24.0
github.com/go-logr/logr v1.4.4 v1.4.4 v1.4.4 v1.4.3 v1.4.4 v1.4.3 v1.4.3 v1.4.3 v1.4.3 v1.4.4 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.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.12.1 v1.11.1 v1.11.1 v1.11.1 v1.11.1 v1.11.1 v1.11.1 v1.11.1 v1.10.0 v1.10.0 — v1.8.4
go.opentelemetry.io/otel v1.47.0 v1.46.0 v1.45.0 v1.44.0 v1.43.0 v1.42.0 v1.39.0 v1.39.0 v1.37.0 v1.36.0 v1.35.0 v1.34.0 v1.24.0
go.opentelemetry.io/otel/metric v1.47.0 v1.46.0 v1.45.0 v1.44.0 v1.43.0 v1.42.0 v1.39.0 v1.39.0 — — — — —
go.opentelemetry.io/otel/sdk/metric v1.47.0 v1.46.0 v1.45.0 v1.44.0 v1.42.0 v1.42.0 v1.39.0 v1.38.0 — — — — —
go.opentelemetry.io/otel/trace v1.47.0 v1.46.0 v1.45.0 v1.44.0 v1.43.0 v1.42.0 v1.39.0 v1.39.0 v1.37.0 v1.36.0 v1.35.0 v1.34.0 v1.24.0
golang.org/x/sys v0.48.0 v0.47.0 v0.47.0 v0.46.0 v0.47.0 v0.41.0 v0.39.0 v0.40.0 v0.47.0 v0.48.0 v0.30.0 v0.30.0 v0.17.0
github.com/google/uuid v1.6.0 v1.6.0 v1.6.0 v1.6.0 v1.6.0 v1.6.0 v1.6.0 v1.6.0 v1.6.0 v1.6.0 v1.6.0 v1.6.0 —
go.uber.org/goleak v1.3.0 v1.3.0 v1.3.0 v1.3.0 v1.3.0 v1.3.0 v1.3.0 v1.3.0 v1.3.0 v1.3.0 v1.3.0 — —

Moved: 8 · 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