CodeSampleX

Recordsgolanggo.opentelemetry.io/otel/sdk/metricv1.44.0go.opentelemetry.io/otel/sdk/metric.DefaultTemporalitySelector

Change the conditions
Fixed
Symbolgo.opentelemetry.io/otel/sdk/metric.DefaultTemporalitySelector
Filter OSubuntu glibc Runtimego 1.26 Package versionv1.44.0 Architecturex64 Package managergo 1 libcglibc Clear filters

Current conditions

go.opentelemetry.io/otel/sdk/metric.DefaultTemporalitySelector @v1.44.0ubuntu glibc · x64 · go 1.26 · go 1

6 of 6 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

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

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 8 · Steady 1

First observed break

v1.44.0

linux · go@1.26

1 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:f124303ba58a624f5c1f48e2f14be2855d9cf70fea96e824a9131f69c5c720bc

Library Version Health Measured there Projects
github.com/go-logr/logr v1.4.3 CANDIDATE Correlated change; unproven combination contract passed 60 project-days
github.com/google/go-cmp v0.7.0 CANDIDATE Correlated change; unproven combination contract passed 60 project-days
github.com/stretchr/testify v1.11.1 CANDIDATE Correlated change; unproven combination contract passed 25 project-days
go.opentelemetry.io/otel v1.44.0 CANDIDATE Correlated change; unproven combination contract passed 60 project-days
go.opentelemetry.io/otel/metric v1.44.0 CANDIDATE Correlated change; unproven combination contract passed 60 project-days
go.opentelemetry.io/otel/metric/x v0.66.0 CANDIDATE Correlated change; unproven combination contract passed 22 project-days
go.opentelemetry.io/otel/sdk v1.44.0 CANDIDATE Correlated change; unproven combination builds observed 60 project-days
go.opentelemetry.io/otel/trace v1.44.0 CANDIDATE Correlated change; unproven combination contract passed 60 project-days
github.com/go-logr/stdr v1.2.2 PASS All observations passed contract passed 60 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: 8 · unchanged at every release: 1

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