CodeSampleX

Recordsgolanggo.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpcv0.61.0go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc.WithMeterProvider

Change the conditions
Fixed
OSdebian glibc Package versionv0.61.0 Symbolgo.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc.WithMeterProvider
Filter Runtimego 1.26 Architecturex64 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc.WithMeterProvider @v0.61.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 (1)

Project observations
1 / 1
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-10-14
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 13 · Steady 2

First observed break

v0.61.0

linux · go@1.26

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

View exact conditions View failure cluster
Library Version Health Measured there Projects
go.opentelemetry.io/otel v1.36.0 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
go.opentelemetry.io/otel v1.42.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
go.opentelemetry.io/otel/metric v1.36.0 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
go.opentelemetry.io/otel/metric v1.42.0 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
go.opentelemetry.io/otel/sdk v1.36.0 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
go.opentelemetry.io/otel/sdk v1.42.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
go.opentelemetry.io/otel/trace v1.36.0 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
go.opentelemetry.io/otel/trace v1.42.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
google.golang.org/grpc v1.72.1 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
google.golang.org/grpc v1.79.2 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
google.golang.org/grpc v1.79.3 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
google.golang.org/protobuf v1.36.11 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
google.golang.org/protobuf v1.36.6 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
github.com/stretchr/testify v1.10.0 PASS All observations passed builds observed 4 project-days
github.com/stretchr/testify v1.11.1 PASS All observations passed 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.

Libraryv0.67.0v0.61.0
go.opentelemetry.io/otel v1.44.0 v1.42.0
go.opentelemetry.io/otel/metric v1.44.0 v1.42.0
go.opentelemetry.io/otel/sdk v1.44.0 v1.42.0
go.opentelemetry.io/otel/trace v1.44.0 v1.42.0
google.golang.org/grpc v1.84.0 v1.79.3
google.golang.org/protobuf v1.36.12 v1.36.11
github.com/stretchr/testify v1.11.1 v1.11.1
go.opentelemetry.io/otel/sdk/metric v1.44.0 —

Moved: 6 · 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