CodeSampleX

Recordsgolangcloud.google.com/go/storage

Compatibility cube

Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.

Fixed
Runtimego@1.26 Package versionv1.10.0

No recorded evidence matches these filters. Nothing is inferred; clear a filter to widen the slice.

The cube reads the newest 6 versions and the first 10 symbols of each, so an empty cell here can mean "outside that window" rather than "never measured".

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 18 · Steady 3

First observed break

v1.10.0

linux · go@1.26

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

Library Version Health Measured there Projects
cloud.google.com/go v0.57.0 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
cloud.google.com/go v0.62.0 CANDIDATE Correlated change; unproven combination builds observed 4 project-days
cloud.google.com/go v0.65.0 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
github.com/golang/protobuf v1.4.2 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
github.com/golang/protobuf v1.5.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
github.com/golang/protobuf v1.5.2 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
github.com/google/go-cmp v0.4.1 CANDIDATE Correlated change; unproven combination builds observed 1 project-day
github.com/google/go-cmp v0.5.1 CANDIDATE Correlated change; unproven combination builds observed 5 project-days
github.com/google/go-cmp v0.5.5 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
github.com/google/go-cmp v0.7.0 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
golang.org/x/oauth2 v0.0.0-20200107190931-bf48bf16ab8d CANDIDATE Correlated change; unproven combination contract passed 6 project-days
golang.org/x/oauth2 v0.0.0-20210514164344-f6687ab2804c CANDIDATE Correlated change; unproven combination builds observed 3 project-days
golang.org/x/oauth2 v0.0.0-20220223155221-ee480838109b CANDIDATE Correlated change; unproven combination builds observed 1 project-day
google.golang.org/genproto v0.0.0-20200618031413-b414f8b61790 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
google.golang.org/genproto v0.0.0-20200804131852-c06518451d9c CANDIDATE Correlated change; unproven combination builds observed 4 project-days
google.golang.org/genproto v0.0.0-20200825200019-8632dd797987 CANDIDATE Correlated change; unproven combination builds observed 5 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
github.com/googleapis/gax-go/v2 v2.0.5 PASS All observations passed contract passed 10 project-days
google.golang.org/api v0.28.0 PASS All observations passed contract passed 1 project-day
google.golang.org/api v0.30.0 PASS All observations passed contract passed 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: 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.