CodeSampleX

Recordsgolangcloud.google.com/go/iamv1.7.0

Change the conditions
Fixed
OSubuntu glibc Package versionv1.7.0
Filter Runtimego 1.26 Symbolwhole package Architecturex64 Package managergo 1 libcglibc Clear filters

Current conditions

cloud.google.com/go/iam @v1.7.0ubuntu glibc · x64 · go 1.26 · go 1

package-level total, not an API

2 of 2 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

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

Dependency Health

Observed combinations and failure evidence for this release

Changed 8 · Steady 0

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

Library Version Health Measured there Projects
cloud.google.com/go v0.123.0 CHANGED Version changed, no linked failure contract passed 2 project-days
cloud.google.com/go/longrunning v0.9.0 CHANGED Version changed, no linked failure builds observed 2 project-days
github.com/googleapis/gax-go/v2 v2.22.0 CHANGED Version changed, no linked failure contract passed 2 project-days
google.golang.org/api v0.277.0 CHANGED Version changed, no linked failure contract passed 2 project-days
google.golang.org/genproto v0.0.0-20260319201613-d00831a3d3e7 CHANGED Version changed, no linked failure builds observed 2 project-days
google.golang.org/genproto/googleapis/api v0.0.0-20260406210006-6f92a3bedf2d CHANGED Version changed, no linked failure contract passed 2 project-days
google.golang.org/grpc v1.81.0 CHANGED Version changed, no linked failure contract passed 2 project-days
google.golang.org/protobuf v1.36.11 CHANGED Version changed, no linked failure contract passed 2 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: 8 · unchanged at every release: 1

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.