Records/golang/google.golang.org/api/failure issue

Where it was measured

PASS means the release recorded a passing observation at PROJECT_COMPILE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

• v0.272.0 PASS 1 passing observations
• v0.180.0 not measured
• v0.176.0 not measured
• v0.54.0 FAIL
• v0.30.0 not measured
• v0.17.0 PASS 1 passing observations
• v0.15.0 FAIL
• v0.14.0 not measured
• v0.13.0 PASS 1 passing observations

Where it reproduced

• os=linux · runtime=go@1.26 ×2 2026-10-18 → 2026-10-22

Nearest known PASS/FAIL boundaries

The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.

• Last passing release v0.13.0 → first failing release v0.15.0

  Releases between them never measured at this stage: 1

  What differs across the boundary

  • github.com/google/go-cmp v0.3.0 → v0.3.0, v0.3.1, v0.4.0 hypothesis
  • golang.org/x/lint v0.0.0-20190409202823-959b441ac422, v0.0.0-20190930215403-16217165b5de → v0.0.0-20190409202823-959b441ac422, v0.0.0-20191125180803-fdd1cda4f05f, v0.0.0-20200130185559-910be7a94367 hypothesis
  • golang.org/x/oauth2 v0.0.0-20190604053449-0f29369cfe45 → v0.0.0-20190604053449-0f29369cfe45, v0.0.0-20191202225959-858c2ad4c8b6, v0.0.0-20200107190931-bf48bf16ab8d hypothesis
  • golang.org/x/sync v0.0.0-20190423024810-112230192c58 → v0.0.0-20190423024810-112230192c58, v0.0.0-20190911185100-cd5d95a43a6e hypothesis
  • golang.org/x/sys v0.0.0-20190507160741-ecd444e8653b, v0.0.0-20190624142023-c5567b49c5d0 → v0.0.0-20190507160741-ecd444e8653b, v0.0.0-20191228213918-04cbcbbfeed8, v0.0.0-20200122134326-e047566fdf82, v0.0.0-20200202164722-d101bd2416d5 hypothesis
  • golang.org/x/tools v0.0.0-20190506145303-2d16b83fe98c, v0.0.0-20191113191852-77e3bb0ad9e7 → v0.0.0-20190506145303-2d16b83fe98c, v0.0.0-20191227053925-7b8e75db28f4, v0.0.0-20200122220014-bf1340f18c4a, v0.0.0-20200204074204-1cc6d1ef6c74 hypothesis
  • google.golang.org/appengine v1.5.0, v1.6.1 → v1.5.0, v1.6.5 hypothesis
  • google.golang.org/genproto v0.0.0-20190502173448-54afdca5d873, v0.0.0-20191108220845-16a3f7862a1a → v0.0.0-20190502173448-54afdca5d873, v0.0.0-20191230161307-f3c370f40bfb, v0.0.0-20200122232147-0452cf42e150, v0.0.0-20200204135345-fa8e72b47b90 hypothesis
  • google.golang.org/grpc v1.20.1, v1.21.1 → v1.20.1, v1.26.0, v1.27.0 hypothesis

  A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.

• Last failing release v0.15.0 → first passing release v0.17.0

  What differs across the boundary

  • github.com/google/go-cmp v0.4.0 → v0.3.0, v0.3.1, v0.4.0 hypothesis
  • golang.org/x/lint v0.0.0-20200130185559-910be7a94367 → v0.0.0-20190409202823-959b441ac422, v0.0.0-20191125180803-fdd1cda4f05f, v0.0.0-20200130185559-910be7a94367 hypothesis
  • golang.org/x/oauth2 v0.0.0-20200107190931-bf48bf16ab8d → v0.0.0-20190604053449-0f29369cfe45, v0.0.0-20191202225959-858c2ad4c8b6, v0.0.0-20200107190931-bf48bf16ab8d hypothesis
  • golang.org/x/sync v0.0.0-20190911185100-cd5d95a43a6e → v0.0.0-20190423024810-112230192c58, v0.0.0-20190911185100-cd5d95a43a6e hypothesis
  • golang.org/x/sys v0.0.0-20200212091648-12a6c2dcc1e4 → v0.0.0-20190507160741-ecd444e8653b, v0.0.0-20191228213918-04cbcbbfeed8, v0.0.0-20200122134326-e047566fdf82, v0.0.0-20200202164722-d101bd2416d5 hypothesis
  • golang.org/x/tools v0.0.0-20200212150539-ea181f53ac56 → v0.0.0-20190506145303-2d16b83fe98c, v0.0.0-20191227053925-7b8e75db28f4, v0.0.0-20200122220014-bf1340f18c4a, v0.0.0-20200204074204-1cc6d1ef6c74 hypothesis
  • google.golang.org/appengine v1.6.5 → v1.5.0, v1.6.5 hypothesis
  • google.golang.org/genproto v0.0.0-20200212174721-66ed5ce911ce → v0.0.0-20190502173448-54afdca5d873, v0.0.0-20191230161307-f3c370f40bfb, v0.0.0-20200122232147-0452cf42e150, v0.0.0-20200204135345-fa8e72b47b90 hypothesis
  • google.golang.org/grpc v1.27.1 → v1.20.1, v1.26.0, v1.27.0 hypothesis
  • honnef.co/go/tools v0.0.1-2019.2.3 → v0.0.0-20190418001031-e561f6794a2a, v0.0.1-2019.2.3 hypothesis

  A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.

• Last passing release v0.17.0 → first failing release v0.54.0

  Releases between them never measured at this stage: 3

  What differs across the boundary

  • cloud.google.com/go — → v0.90.0, v0.93.3 hypothesis
  • github.com/google/go-cmp v0.4.0 → v0.5.6, v0.5.9 hypothesis
  • golang.org/x/lint v0.0.0-20200130185559-910be7a94367 → v0.0.0-20210508222113-6edffad5e616 hypothesis
  • golang.org/x/net — → v0.0.0-20210503060351-7fd8e65b6420, v0.0.0-20211112202133-69e39bad7dc2 hypothesis
  • golang.org/x/oauth2 v0.0.0-20200107190931-bf48bf16ab8d → v0.0.0-20210805134026-6f1e6394065a hypothesis
  • golang.org/x/sync v0.0.0-20190911185100-cd5d95a43a6e → v0.0.0-20210220032951-036812b2e83c hypothesis
  • golang.org/x/sys v0.0.0-20200212091648-12a6c2dcc1e4 → v0.0.0-20210806184541-e5e7981a1069, v0.8.0, v0.9.0 hypothesis
  • golang.org/x/tools v0.0.0-20200212150539-ea181f53ac56 → v0.1.5 hypothesis
  • google.golang.org/appengine v1.6.5 → v1.6.7 hypothesis
  • google.golang.org/genproto v0.0.0-20200212174721-66ed5ce911ce → v0.0.0-20210805201207-89edb61ffb67, v0.0.0-20210821163610-241b8fcbd6c8 hypothesis
  • google.golang.org/grpc v1.27.1 → v1.39.1, v1.40.0 hypothesis
  • honnef.co/go/tools v0.0.1-2019.2.3 → — hypothesis

  A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.

• Last failing release v0.54.0 → first passing release v0.272.0

  Releases between them never measured at this stage: 3

  What differs across the boundary

  • cloud.google.com/go — → v0.90.0, v0.93.3 hypothesis
  • cloud.google.com/go/auth v0.18.2 → — hypothesis
  • cloud.google.com/go/auth/oauth2adapt v0.2.8 → — hypothesis
  • cloud.google.com/go/compute/metadata v0.9.0 → — hypothesis
  • github.com/google/go-cmp v0.7.0 → v0.5.6, v0.5.9 hypothesis
  • github.com/google/s2a-go v0.1.9 → — hypothesis
  • github.com/google/uuid v1.6.0 → — hypothesis
  • github.com/googleapis/enterprise-certificate-proxy v0.3.14 → — hypothesis
  • github.com/googleapis/gax-go/v2 v2.19.0, v2.21.0 → v2.0.5 hypothesis
  • go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc v0.61.0 → — hypothesis
  • go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.61.0 → — hypothesis
  • golang.org/x/lint — → v0.0.0-20210508222113-6edffad5e616 hypothesis
  • golang.org/x/net v0.52.0, v0.53.0 → v0.0.0-20210503060351-7fd8e65b6420, v0.0.0-20211112202133-69e39bad7dc2 hypothesis
  • golang.org/x/oauth2 v0.36.0 → v0.0.0-20210805134026-6f1e6394065a hypothesis
  • golang.org/x/sync v0.20.0 → v0.0.0-20210220032951-036812b2e83c hypothesis
  • golang.org/x/sys — → v0.0.0-20210806184541-e5e7981a1069, v0.8.0, v0.9.0 hypothesis
  • golang.org/x/time v0.15.0 → — hypothesis
  • golang.org/x/tools — → v0.1.5 hypothesis
  • google.golang.org/appengine — → v1.6.7 hypothesis
  • google.golang.org/genproto — → v0.0.0-20210805201207-89edb61ffb67, v0.0.0-20210821163610-241b8fcbd6c8 hypothesis
  • google.golang.org/genproto/googleapis/bytestream v0.0.0-20260311181403-84a4fc48630c → — hypothesis
  • google.golang.org/genproto/googleapis/rpc v0.0.0-20260316180232-0b37fe3546d5, v0.0.0-20260414002931-afd174a4e478 → — hypothesis
  • google.golang.org/grpc v1.79.2, v1.82.0 → v1.39.1, v1.40.0 hypothesis
  • google.golang.org/protobuf v1.36.11 → — hypothesis

  A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.

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: 21 · unchanged at every release: 4

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.

Evidence gaps

• Releases in this window never measured at PROJECT_COMPILE: 4
• No failure domain was inferred for this failure.

Published answers for the affected releases

• google.golang.org/api v0.54.0: googleapi.CheckResponse Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgoogle.golang.org/api/googleapi.CheckResponse MIT-0 · 2026-10-22
• google.golang.org/api v0.54.0 Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW MIT-0 · 2026-10-22
• google.golang.org/api v0.15.0 Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW MIT-0 · 2026-10-18