CodeSampleX

Recordsgolanggo.opentelemetry.io/proto/otlpv1.7.1go.opentelemetry.io/proto/otlp/resource/v1

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

Current conditions

go.opentelemetry.io/proto/otlp/resource/v1 @v1.7.1ubuntu glibc · x64 · go 1.26 · go 1

5 of 5 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

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

Dependency Health

Observed combinations and failure evidence for this release

Changed 3 · Steady 0

Dependency changes observed: 3. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
github.com/grpc-ecosystem/grpc-gateway/v2 v2.27.1 CHANGED Version changed, no linked failure nothing measured 1 project-day
google.golang.org/grpc v1.74.2 CHANGED Version changed, no linked failure nothing measured 1 project-day
google.golang.org/protobuf v1.36.12 CHANGED Version changed, no linked failure contract passed 1 project-day

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.