CodeSampleX

Recordsgolanggo.opentelemetry.io/otel/sdk/metricv1.45.0NewMeterProvider

Change the conditions
Fixed
OSdebian glibc SymbolNewMeterProvider Architecturex64
Filter Runtimego 1.26 Package versionv1.45.0 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

NewMeterProvider @v1.45.0debian glibc · x64 · go 1.26 · go · go

1 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (2)

Project observations
4 / 4
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-09-17
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 8 · Steady 1

First observed break

v1.45.0

linux · go@1.26

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

View exact conditions View failure cluster
Library Version Health Measured there Projects
github.com/go-logr/logr v1.4.4 CANDIDATE Correlated change; unproven combination contract passed 20 project-days
github.com/google/go-cmp v0.7.0 CANDIDATE Correlated change; unproven combination contract passed 20 project-days
github.com/stretchr/testify v1.11.1 CANDIDATE Correlated change; unproven combination contract passed 20 project-days
go.opentelemetry.io/otel v1.45.0 CANDIDATE Correlated change; unproven combination contract passed 20 project-days
go.opentelemetry.io/otel/metric v1.45.0 CANDIDATE Correlated change; unproven combination builds observed 20 project-days
go.opentelemetry.io/otel/metric/x v0.67.0 CANDIDATE Correlated change; unproven combination builds observed 7 project-days
go.opentelemetry.io/otel/sdk v1.45.0 CANDIDATE Correlated change; unproven combination contract passed 20 project-days
go.opentelemetry.io/otel/trace v1.45.0 CANDIDATE Correlated change; unproven combination contract passed 20 project-days
github.com/go-logr/stdr v1.2.2 PASS All observations passed contract passed 20 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.46.0v1.45.0v1.44.0v1.43.0v1.37.0v1.34.0
github.com/go-logr/logr v1.4.4 v1.4.4 v1.4.3 v1.4.3 v1.4.3 v1.4.2
github.com/google/go-cmp v0.7.0 v0.7.0 v0.7.0 v0.7.0 v0.7.0 v0.6.0
github.com/stretchr/testify v1.12.1 v1.11.1 — v1.11.1 v1.11.1 v1.10.0
go.opentelemetry.io/otel v1.46.0 v1.45.0 v1.44.0 v1.43.0 v1.37.0 v1.34.0
go.opentelemetry.io/otel/metric v1.46.0 v1.45.0 v1.44.0 v1.43.0 v1.37.0 v1.34.0
go.opentelemetry.io/otel/metric/x v0.68.0 v0.67.0 — — — —
go.opentelemetry.io/otel/sdk v1.46.0 v1.45.0 v1.44.0 v1.43.0 v1.37.0 v1.34.0
go.opentelemetry.io/otel/trace v1.46.0 v1.45.0 v1.44.0 v1.43.0 v1.37.0 v1.34.0
github.com/go-logr/stdr v1.2.2 v1.2.2 v1.2.2 v1.2.2 v1.2.2 v1.2.2

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