CodeSampleX

Recordsgolanggithub.com/googleapis/gax-go/v2v2.0.5

Change the conditions
Fixed
OSdebian glibc Package versionv2.0.5
Filter Runtimego 1.26 Symbolwhole package Architecturex64 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

github.com/googleapis/gax-go/v2 @v2.0.5debian glibc · x64 · go 1.26 · go · go

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
6
Independent reporting peers
1
Last recorded
2026-10-09

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 0

First observed break

v2.0.5

linux · go@1.26

2 FAIL · stage: PROJECT_RESOLVE · fingerprint: sha256:960c448010d338b23e4225acf905c3ba5fc46c4e38004ca42dccb0ec225d0a82

Library Version Health Measured there Projects
google.golang.org/grpc v1.28.0 CANDIDATE Correlated change; unproven combination builds observed 2 project-days
google.golang.org/grpc v1.29.1 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
google.golang.org/grpc v1.31.0 CANDIDATE Correlated change; unproven combination builds observed 9 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: 10 · 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