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

Where it was measured

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

• v0.298.0 PASS 4 passing observations
• v0.293.0 PASS 2 passing observations
• v0.288.0 PASS 4 passing observations
• v0.287.1 FAIL
• v0.277.0 PASS 9 passing observations
• v0.274.0 PASS 6 passing observations
• v0.273.1 FAIL
• v0.272.0 not measured
• v0.264.0 PASS 8 passing observations

Where it reproduced

• executionContext=go · os=linux · runtime=go@1.26 ×2 2026-10-14 → 2026-10-14
• executionContext=go · moduleSystem=go.mod · os=linux · runtime=go@1.26 ×1 2026-10-12 → 2026-10-12

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.264.0 → first failing release v0.273.1

  Releases between them never measured at this stage: 1

  What differs across the boundary

  • cloud.google.com/go/auth v0.18.1 → v0.18.2 hypothesis
  • github.com/googleapis/enterprise-certificate-proxy v0.3.11 → v0.3.14 hypothesis
  • github.com/googleapis/gax-go/v2 v2.16.0, v2.17.0 → v2.19.0, v2.20.0 hypothesis
  • golang.org/x/net v0.49.0 → v0.52.0 hypothesis
  • golang.org/x/oauth2 v0.34.0 → v0.36.0 hypothesis
  • golang.org/x/sync v0.19.0 → v0.20.0 hypothesis
  • golang.org/x/time v0.14.0 → v0.15.0 hypothesis
  • google.golang.org/genproto/googleapis/bytestream v0.0.0-20260122232226-8e98ce8d340d → v0.0.0-20260319201613-d00831a3d3e7 hypothesis
  • google.golang.org/genproto/googleapis/rpc v0.0.0-20260122232226-8e98ce8d340d, v0.0.0-20260128011058-8636f8732409 → v0.0.0-20260319201613-d00831a3d3e7, v0.0.0-20260401001100-f93e5f3e9f0f hypothesis
  • google.golang.org/grpc v1.78.0 → v1.79.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.273.1 → first passing release v0.274.0

  What differs across the boundary

  • github.com/googleapis/gax-go/v2 v2.19.0, v2.21.0 → v2.19.0, v2.20.0 hypothesis
  • google.golang.org/grpc v1.79.3, v1.80.0 → v1.79.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.277.0 → first failing release v0.287.1

  What differs across the boundary

  • github.com/googleapis/enterprise-certificate-proxy v0.3.15 → v0.3.17 hypothesis
  • github.com/googleapis/gax-go/v2 v2.22.0 → v2.22.0, v2.23.0 hypothesis
  • go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.68.0 → v0.67.0 hypothesis
  • golang.org/x/net v0.55.0 → v0.56.0, v0.58.0 hypothesis
  • golang.org/x/sync v0.20.0 → v0.21.0, v0.22.0 hypothesis
  • google.golang.org/genproto/googleapis/bytestream — → v0.0.0-20260630182238-925bb5da69e7 hypothesis
  • google.golang.org/genproto/googleapis/rpc v0.0.0-20260427160629-7cedc36a6bc4 → v0.0.0-20260630182238-925bb5da69e7 hypothesis
  • google.golang.org/grpc v1.81.0 → v1.82.0, v1.83.2 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.287.1 → first passing release v0.288.0

  What differs across the boundary

  • cloud.google.com/go/auth v0.18.2, v0.20.0, v0.24.1 → v0.20.0 hypothesis
  • github.com/googleapis/enterprise-certificate-proxy v0.3.11, v0.3.17 → v0.3.17 hypothesis
  • github.com/googleapis/gax-go/v2 v2.22.0, v2.24.0, v2.26.2 → v2.22.0, v2.23.0 hypothesis
  • go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc v0.61.0, v0.67.0 → v0.67.0 hypothesis
  • go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.61.0, v0.67.0 → v0.67.0 hypothesis
  • golang.org/x/oauth2 v0.32.0, v0.36.0 → v0.36.0 hypothesis
  • golang.org/x/sync v0.19.0, v0.21.0, v0.22.0 → v0.21.0, v0.22.0 hypothesis
  • golang.org/x/time v0.14.0, v0.15.0 → v0.15.0 hypothesis
  • google.golang.org/genproto/googleapis/rpc v0.0.0-20260630182238-925bb5da69e7, v0.0.0-20260715232425-e75dac1f907d → v0.0.0-20260630182238-925bb5da69e7 hypothesis
  • google.golang.org/grpc v1.82.0, v1.82.1, v1.83.2 → v1.82.0, v1.83.2 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: 13 · unchanged at every release: 5

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

• The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
• Releases in this window never measured at PROJECT_TEST: 1
• No failure domain was inferred for this failure.

Published answers for the affected releases

• google.golang.org/api v0.287.1: bundler.ErrOverflow 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/support/bundler.ErrOverflowgo 1.26 MIT-0 · 2026-10-12
• google.golang.org/api v0.287.1: bundler.ErrOversizedItem 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/support/bundler.ErrOversizedItem MIT-0 · 2026-10-12
• google.golang.org/api v0.287.1: bundler.Bundler 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/support/bundler.Bundlergo 1.26.6 MIT-0 · 2026-10-12
• google.golang.org/api v0.273.1: option.WithEndpoint 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/option.WithEndpointgo 1.26 MIT-0 · 2026-10-14
• google.golang.org/api v0.273.1: option.WithoutAuthentication 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. HOWoption.WithoutAuthentication MIT-0 · 2026-10-14
• google.golang.org/api v0.273.1: googleapi.Error 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.Error MIT-0 · 2026-10-14