$ cat google/week/2026-10-12.log
the week in review · Oct 12 – Oct 18, 2026
Bound ID tokens become the Cloud Run default in google-auth 2.62.0
By RepoJournal · composed from the cited sources · human-reviewed weekly · methodology
At the same time, python-genai 2.30.0 rebuilt streaming continuation, and JAX spent the week correcting numerical edges in stats, linalg, and sharding.
google-auth: v2.62.0 googleapis/google-cloud-python
by release-please[bot]
Version 2.62.0 flips the auth library's behavior so bound ID tokens are the default on Cloud Run. Anything downstream that validates tokens minted there, proxies, gateways, or your own middleware, needs checking against the new binding rather than assuming the previous default.
fix: resume streaming generation from the latest checkpoint continuation token on mid-stream errors or cutoffs googleapis/python-genai
Streaming generation now resumes from the latest checkpoint continuation token after a mid-stream error or cutoff instead of dropping the turn. This is the fix that makes long responses survivable on flaky connections; the 2.30.0 release notes say it will "resume streaming generation from the latest checkpoint continuation token on mid-stream errors or cutoffs."
feat: accumulate streaming continuation usage metadata and expose initial_prompt_token_count googleapis/python-genai
Continuation usage metadata now accumulates across a continued stream, and initial_prompt_token_count is exposed separately. Token accounting for resumed generations stops undercounting the prompt side, which matters if you bill or budget off those numbers.
fix: make continuation streams retry dropped hops, stop on prompt_feedback, and keep real errors in generate_content googleapis/python-genai
Continuation streams retry dropped hops and stop on prompt_feedback, while generate_content keeps real errors instead of swallowing them. Retry logic you wrote around the old behavior may now be redundant, or masks errors the SDK already surfaces.
fix: clear intermediate CONTINUATION finish_reason in streaming continuation googleapis/python-genai
Intermediate CONTINUATION finish reasons are cleared so consumers no longer see a spurious completion in the middle of a resumed stream. Clients that branch on finish_reason were reading those as end-of-turn.
fix(google-cloud-spanner): clear buffered DDL statements on rollback and flush on autocommit googleapis/google-cloud-python
With autocommit=False, DDL buffered on a DBAPI cursor is now cleared on rollback and flushed on autocommit, closing a path where statements stayed queued past the transaction that should have owned them. Paired with the related change keeping DDL out of transaction retries, the Spanner DBAPI layer's DDL handling is now consistent across the three cases.
Add `jax.sharding.no_collectives` context manager to forbid collectives on specified axes. google/jax
jax.sharding.no_collectives fails at trace time in explicit sharding mode when an operation or reshard introduces a collective across a forbidden mesh axis, raising core.ForbiddenCollectiveError. It turns a silent cross-slice all-reduce into a compile-time error, which is what you want before the cluster bill tells you.
Propagate scatter mode through scatter_max/min JVP google/jax
The scatter_max/min JVP passed the scatter mode only to its final scatter_add, so internal gathers and scatter_adds used default FILL_OR_DROP and silently dropped out-of-bounds updates. With mode="clip", those dropped updates made num_updates 0 and produced wrong gradients.
$ ls google/week/ # the briefings behind this review
Keep up with Google in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.
fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.
Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.