CodeSampleX

Recordsgolanggo.opentelemetry.io/otelv1.28.0propagation.HeaderCarrier

Change the conditions
Fixed
Package versionv1.28.0 Symbolpropagation.HeaderCarrier
Filter OSalpine musl Runtimego 1.26 Architecturex64 Package managergo modules Execution contextgo libcmusl Clear filters

Current conditions

propagation.HeaderCarrier @v1.28.0alpine musl · x64 · go 1.26 · go modules · 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 (1)

Project observations
nothing at this coordinate
Contract verifications
2 / 2
Cross-checked
reproduced by two or more independent peers
Last recorded
2026-08-18

Dependency Health

Observed combinations and failure evidence for this release

Changed 3 · Steady 1

Dependency changes observed: 3. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
github.com/go-logr/logr v1.4.2 CHANGED Version changed, no linked failure contract passed 1 project-day
go.opentelemetry.io/otel/metric v1.28.0 CHANGED Version changed, no linked failure builds observed 1 project-day
go.opentelemetry.io/otel/trace v1.28.0 CHANGED Version changed, no linked failure builds observed 1 project-day
github.com/go-logr/stdr v1.2.2 PASS All observations passed contract passed 1 project-day

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: 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.