CodeSampleX

Recordsgolanggo.opentelemetry.io/otel/metric/xv0.68.0go.opentelemetry.io/otel/metric/x.Settable

Change the conditions
Fixed
Symbolgo.opentelemetry.io/otel/metric/x.Settable libcglibc
Filter OSubuntu glibc Runtimego 1.26 Package versionv0.68.0 Architecturex64 Package managergo 1 Clear filters

Current conditions

go.opentelemetry.io/otel/metric/x.Settable @v0.68.0ubuntu glibc · x64 · go 1.26 · go 1

1 of 1 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

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

Dependency Health

Observed combinations and failure evidence for this release

Changed 2 · Steady 0

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

Library Version Health Measured there Projects
go.opentelemetry.io/otel v1.46.0 CHANGED Version changed, no linked failure contract passed 13 project-days
go.opentelemetry.io/otel/metric v1.46.0 CHANGED Version changed, no linked failure contract passed 13 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.