CodeSampleX

Recordsgolanggo.opentelemetry.io/contrib/instrumentation/net/http/otelhttp

Compatibility cube

Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.

Fixed
Runtimego@1.26 Package versionv0.70.0

No recorded evidence matches these filters. Nothing is inferred; clear a filter to widen the slice.

The cube reads the newest 6 versions and the first 10 symbols of each, so an empty cell here can mean "outside that window" rather than "never measured".

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 7 · Steady 0

First observed break

v0.70.0

linux · go@1.26

1 FAIL · stage: PROJECT_RESOLVE · fingerprint: sha256:4c982a152e43e734c654d84887617e4df1a718080bbc91bfba97b3ee9e535ef5

Library Version Health Measured there Projects
github.com/felixge/httpsnoop v1.1.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
github.com/stretchr/testify v1.11.1 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
go.opentelemetry.io/otel v1.45.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
go.opentelemetry.io/otel/metric v1.45.0 CANDIDATE Correlated change; unproven combination builds observed 2 project-days
go.opentelemetry.io/otel/sdk v1.45.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
go.opentelemetry.io/otel/sdk/metric v1.45.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
go.opentelemetry.io/otel/trace v1.45.0 CANDIDATE Correlated change; unproven combination contract passed 2 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: 7 · 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.