189 wires and counting

$ follow Google

Keep up with Google in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

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.

$ status

wire 2026-10-27
stories 71

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

Pallas rejects kernel writes to immutable inputs

By RepoJournal · Filed · About Google · Composed from the cited sources · methodology

JAX's Pallas front end got stricter in two places at once: pl.kernel now raises on writes to plain array inputs that were silently dropped before, and a deprecated transpose_ref path is gone, while the Python client libraries added a new observability package and moved Spanner tests off live instances.

[pallas] Raise when an mpmd_map (pl.kernel) kernel writes to an immutable array input. google/jax

by Robert Dyro

mpmd_map, and therefore pl.kernel, passed every input to the kernel as a Ref but only discharged writes for inputs that were Refs at the call site, so writes to plain array inputs vanished from the effects while the kernel mutated an HLO operand XLA treats as read-only. Existing kernels that relied on that silent path now raise a ValueError naming the input and pointing at jax.new_ref or out_type.

[Pallas:MGPU] Remove deprecated `plgpu.transpose_ref`. google/jax

by Allan Renucci

The transpose_ref implementation is deleted from core.py and its entry in mosaic_gpu.py is finalized to None until JAX v0.13.0. Pallas MGPU code still calling plgpu.transpose_ref has no implementation left to land on.

Fix value-level set_xla_metadata() when an op's output is wrapped in sdy.sharding_constraint. google/jax

by jax authors

Value-level set_xla_metadata() attached metadata to the sdy.sharding_constraint wrapper instead of the underlying op, which Shardy later drops, and this bit ops such as fori_loop on meshes with mixed or explicit sharding. The fix retargets the metadata at the op the constraint wraps.

google-cloud-observability: v0.1.0 googleapis/google-cloud-python

by release-please[bot]

The first release of google-cloud-observability lands at v0.1.0 with the google/cloud/observability/v1 surface. Expect the usual 0.x churn before you build against it.

refactor(gapic-generator): align telemetry compliance matrix and test engine with tidy data googleapis/google-cloud-python

by chalmerlowe

The rest of the day is housekeeping. The OpenTelemetry compliance matrix was reshaped from one row per RPC to one row per span, the Spanner admin and DB-API DDL system tests were consolidated onto mock servers to cut LRO latency and flakiness, and Bazel moved from 9.2.0 to 9.3.1, which drops the distrusted eMudhra and Sectigo AAA root CAs from the bundled JDK.

Quick answers

What shipped in Google on October 27, 2026?
JAX's Pallas front end got stricter in two places at once: pl.kernel now raises on writes to plain array inputs that were silently dropped before, and a deprecated transpose_ref path is gone, while the Python client libraries added a new observability package and moved Spanner tests off live instances. In total, 37 commits, 32 pull requests, and 2 releases landed.
Who contributed to Google on October 27, 2026?
8 developers shipped this update, including Allan Renucci, Robert Dyro, Vladimir Belitskiy, Naums Mogers, jax authors, release-please[bot], chalmerlowe, and olavloite.
What were the notable Google updates?
[pallas] Raise when an mpmd_map (pl.kernel) kernel writes to an immutable array input, [Pallas:MGPU] Remove deprecated `plgpu.transpose_ref`, and Fix value-level set_xla_metadata() when an op's output is wrapped in sdy.sharding_constraint.