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

Where it was measured

PASS means the release recorded a passing observation at PROJECT_RESOLVE 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 not measured
• v0.293.0 FAIL
• v0.287.1 not measured
• v0.277.0 not measured
• v0.274.0 not measured

Where it reproduced

• os=linux · runtime=go@1.26 ×1 2026-09-19 → 2026-09-19

Nearest known PASS/FAIL boundaries

No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.

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

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

• No release in this window recorded a passing observation at PROJECT_RESOLVE.
• Releases in this window never measured at PROJECT_RESOLVE: 4
• No failure domain was inferred for this failure.

Published answers for the affected releases

• google.golang.org/api v0.293.0: iterator.Done, iterator.NewPageInfo, iterator.NewPager 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/iterator.Donegoogle.golang.org/api/iterator.NewPageInfogoogle.golang.org/api/iterator.NewPagergoogle.golang.org/api/support/bundler.NewBundlergo 1.26.6 MIT-0 · 2026-10-05