CodeSampleX

Recordsgolanggo.opentelemetry.io/proto/otlpv1.5.0go.opentelemetry.io/proto/otlp/trace/v1.Span

Change the conditions
Fixed
Symbolgo.opentelemetry.io/proto/otlp/trace/v1.Span
Filter OSubuntu glibc Runtimego 1.26 Package versionv1.5.0 Architecturex64 Package managergo 1 libcglibc Clear filters

Current conditions

go.opentelemetry.io/proto/otlp/trace/v1.Span @v1.5.0ubuntu glibc · x64 · go 1.26 · go 1

5 of 6 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

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

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 0

First observed break

v1.5.0

linux · go@1.26

1 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:089d53aa715fcac682a38976c28f89082d3b26eecd5702f323784a1bc5de5112

Library Version Health Measured there Projects
github.com/grpc-ecosystem/grpc-gateway/v2 v2.26.1 CANDIDATE Correlated change; unproven combination builds observed 7 project-days
google.golang.org/grpc v1.71.0 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
google.golang.org/protobuf v1.36.5 CANDIDATE Correlated change; unproven combination contract passed 7 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: 3 · 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