CodeSampleX

Recordsgolanggo.opentelemetry.io/otel/metricv1.35.0Float64Histogram

Change the conditions
Fixed
SymbolFloat64Histogram Package managergo 1
Filter OSubuntu glibc Runtimego 1.26 Package versionv1.35.0 Architecturex64 libcglibc Clear filters

Current conditions

Float64Histogram @v1.35.0ubuntu glibc · x64 · go 1.26 · go 1

4 of 4 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (2)

Project observations
4 / 4
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-08-20

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 0

First observed break

v1.35.0

go@1.26

3 FAIL · stage: PROJECT_TEST

Library Version Health Measured there Projects
github.com/stretchr/testify v1.10.0 CANDIDATE Correlated change; unproven combination builds observed 7 project-days
go.opentelemetry.io/otel v1.35.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.

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