CodeSampleX

Recordsgolanggo.opentelemetry.io/otel/metricv1.34.0

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

Current conditions

go.opentelemetry.io/otel/metric @v1.34.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
4
Independent reporting peers
1
Last recorded
2026-10-15
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

v1.34.0

linux · go@1.26

1 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:089d53aa715fcac682a38976c28f89082d3b26eecd5702f323784a1bc5de5112

View exact conditions View failure cluster
Library Version Health Measured there Projects
go.opentelemetry.io/otel v1.34.0 CANDIDATE Correlated change; unproven combination contract passed 7 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.28.0v1.24.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.38.0 v1.37.0 v1.36.0 v1.35.0 v1.34.0 v1.28.0 v1.24.0

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