CodeSampleX

Recordsgolanggo.opentelemetry.io/otel/metricv1.24.0

Change the conditions
Fixed
OSwindows 11 Package versionv1.24.0
Filter Runtimego 1.26 Symbolwhole package Architecturex64 Package managergo 1 Clear filters

Current conditions

go.opentelemetry.io/otel/metric @v1.24.0windows 11 · x64 · go 1.26 · go 1

package-level total, not an API

3 of 4 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (15)

Project observations
3 / 4
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Failures with a captured fingerprint
0 / 1
Last recorded
2026-08-17
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 0

First observed break

v1.24.0

linux · go@1.26

8 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:c2ae6d87252c4f443f14d40584c4012a25213fbf0bb7b5e35604e6d35d608229

View exact conditions View failure cluster
Library Version Health Measured there Projects
github.com/stretchr/testify v1.8.4 CANDIDATE Correlated change; unproven combination contract passed 17 project-days
go.opentelemetry.io/otel v1.24.0 CANDIDATE Correlated change; unproven combination contract passed 17 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.35.0v1.34.0v1.28.0v1.24.0
github.com/stretchr/testify v1.12.1 v1.11.1 v1.11.1 v1.11.1 v1.11.1 v1.10.0 — — v1.8.4
go.opentelemetry.io/otel v1.46.0 v1.45.0 v1.44.0 v1.43.0 v1.37.0 v1.35.0 v1.34.0 v1.28.0 v1.24.0

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.

Recent failure clusters