CodeSampleX

Recordsgolanggo.opentelemetry.io/otel/sdk/metricv1.43.0go.opentelemetry.io/otel/sdk/metric.AggregationExplicitBucketHistogram

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

Current conditions

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

3 of 4 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

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

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 7 · Steady 1

First observed break

v1.43.0

linux · go@1.26

4 FAIL · stage: UNKNOWN · fingerprint: sha256:69d280c75213cffbfefa3920bca150e41e4eb0ce94d677766c799d026fb7e8fa

Library Version Health Measured there Projects
github.com/go-logr/logr v1.4.3 CANDIDATE Correlated change; unproven combination contract passed 46 project-days
github.com/google/go-cmp v0.7.0 CANDIDATE Correlated change; unproven combination contract passed 44 project-days
github.com/stretchr/testify v1.11.1 CANDIDATE Correlated change; unproven combination contract passed 44 project-days
go.opentelemetry.io/otel v1.43.0 CANDIDATE Correlated change; unproven combination contract passed 46 project-days
go.opentelemetry.io/otel/metric v1.43.0 CANDIDATE Correlated change; unproven combination contract passed 46 project-days
go.opentelemetry.io/otel/sdk v1.43.0 CANDIDATE Correlated change; unproven combination contract passed 46 project-days
go.opentelemetry.io/otel/trace v1.43.0 CANDIDATE Correlated change; unproven combination contract passed 46 project-days
github.com/go-logr/stdr v1.2.2 PASS All observations passed contract passed 46 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

Showing the 12 most-reported of 24 recorded failure clusters. The rest are single reports.