CodeSampleX

Recordsgolangcloud.google.com/go/longrunningv0.5.7

Change the conditions
Fixed
Package versionv0.5.7
Filter OSalpine musl Runtimego 1.26 Symbolwhole package Architecturex64 Package managergo Execution contextgo libcmusl Clear filters

Current conditions

cloud.google.com/go/longrunning @v0.5.7alpine musl · 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
1
Independent reporting peers
1
Last recorded
2026-09-07

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.112.1 CHANGED Version changed, no linked failure nothing measured 1 project-day
github.com/googleapis/gax-go/v2 v2.12.4 CHANGED Version changed, no linked failure builds observed 1 project-day
google.golang.org/api v0.180.0 CHANGED Version changed, no linked failure builds observed 1 project-day
google.golang.org/genproto v0.0.0-20240401170217-c3f982113cda CHANGED Version changed, no linked failure builds observed 1 project-day
google.golang.org/genproto/googleapis/api v0.0.0-20241007155032-5fefd90f89a9 CHANGED Version changed, no linked failure contract passed 1 project-day
google.golang.org/genproto/googleapis/rpc v0.0.0-20241007155032-5fefd90f89a9 CHANGED Version changed, no linked failure contract passed 1 project-day
google.golang.org/grpc v1.67.1 CHANGED Version changed, no linked failure contract passed 1 project-day
google.golang.org/protobuf v1.35.1 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: 8 · 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.