$ the-wire · showcase
Bound ID tokens on Cloud Run by default, python-genai v2.30.0 adds continuation metadata
By RepoJournal · Filed · About Google · Composed from the cited sources · methodology
google-auth 2.62.0 flips bound ID tokens on by default for Cloud Run, python-genai 2.30.0 ships streaming continuation usage accounting, and db-dtypes closes its pandas 3.1 gaps before the release lands.
google-auth: v2.62.0 googleapis/google-cloud-python
by release-please[bot]
google-auth v2.62.0 enables bound ID tokens by default on Cloud Run. Anyone fetching ID tokens from that metadata server gets the bound form without opting in, so verify your verifier and audience checks handle it before you upgrade.
v2.30.0 googleapis/python-genai
by release-please[bot]
v2.30.0 accumulates streaming continuation usage metadata and exposes initial_prompt_token_count, and adds continuation_token to the Interactions interaction.status_update event. Code that sums token usage across multi-hop continuations now has an explicit running count instead of reconstructing it.
feat(db-dtypes): support pandas 3.1 (#18590) googleapis/google-cloud-python
db-dtypes gained pandas 3.1 support by dropping references to an internal, removed variable and patching the other breakages its pre-release tests exposed. Without it, db-dtypes fails against the upcoming pandas release.
fix(google-cloud-spanner): do not replay DDL statements on transaction retry googleapis/google-cloud-python
Spanner DBAPI no longer replays DDL on transaction retry: StatementType.DDL executions are excluded from TransactionRetryHelper, so an aborted transaction can no longer rerun DDL statements that execute outside the read-write transaction or re-queue DDLs already applied.
[pallas:tpu] Avoid redundant float32 round-trip and duplicate setup in TPU paged_attention_kernel. google/jax
The TPU paged_attention_kernel dropped a float32 round-trip in MultiPageAsyncCopyDescriptor.wait_and_get_loaded, where unquantized bfloat16 KV pages were being cast to float32 and immediately back by _maybe_dequantize. Also in the long tail: lax.rem picked up precision tests across bfloat16 through float64, Mosaic GPU deleted serde.cc downgrade rules now that the forward-compatible IR version i...