CodeSampleX

Recordsgolanggo.opentelemetry.io/otel/metricv1.45.0

Change the conditions
Fixed
OSdebian glibc Package versionv1.45.0
Filter Runtimego 1.26 Symbolwhole package Architecturex64 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

go.opentelemetry.io/otel/metric @v1.45.0debian glibc · x64 · go 1.26 · go · go

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
3
Independent reporting peers
1
Last recorded
2026-09-16

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 0

First observed break

v1.45.0

linux · go@1.26

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

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