CodeSampleX

Recordsgolanggo.opentelemetry.io/contrib/bridges/prometheusv0.68.0go.opentelemetry.io/contrib/bridges/prometheus.WithGatherer

Change the conditions
Fixed
Package versionv0.68.0 Symbolgo.opentelemetry.io/contrib/bridges/prometheus.WithGatherer
Filter OSubuntu glibc Runtimego 1.26 Architecturex64 Package managergo 1 libcglibc Clear filters

Current conditions

go.opentelemetry.io/contrib/bridges/prometheus.WithGatherer @v0.68.0ubuntu glibc · x64 · go 1.26 · go 1

3 of 3 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

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

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 5 · Steady 1

First observed break

v0.68.0

linux · go@1.26

5 FAIL · stage: UNKNOWN · fingerprint: sha256:5782351ae918be51270d9cef1bb673332e715560dfddd80edfbf5b54ef128219

Library Version Health Measured there Projects
github.com/prometheus/client_golang v1.23.2 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
github.com/stretchr/testify v1.11.1 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
go.opentelemetry.io/otel v1.43.0 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
go.opentelemetry.io/otel/sdk v1.43.0 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
go.opentelemetry.io/otel/sdk/metric v1.43.0 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
github.com/prometheus/client_model v0.6.2 PASS All observations passed contract passed 3 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: 5 · unchanged at every release: 2

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