Who contributed to Google on May 30, 2026?

3 developers shipped this update, including TheSkyentist, chalmerlowe, and parthea.

What were the notable Google updates?

Make warnings about security on the compilation cache warnings, Remove setting `Manual` HloSharding directly as it would be anyways ignored during Shardy import. If required, JAX NamedSharding should be set instead which would be correctly lowered to corresponding, and scipy.special: add dawsn (Dawson's integral).

Google

JAX, the GenAI SDK, and the Cloud libs - Google's open source layer

Pick a date

Topics: AI / ML Python Full archive →

The Wire · Showcase

JAX tightens compilation cache security while Google Cloud standardizes Spanner connections

By RepoJournal · Filed 06:03 UTC on May 30, 2026 · About Google

3 people shipped this

parthea @parthea 2 cited

TheSkyentist @TheSkyentist 1 cited

chalmerlowe @chalmerlowe 1 cited

JAX shipped critical warnings for unsafe compilation cache practices, forcing a breaking change in how you specify distributed sharding across the stack.

JAX is hardening its compilation cache with mandatory security warnings [1] that will surface in API docs, addressing a vulnerability surface that's been quietly dangerous. In the same pass, JAX is ripping out the `Manual` HloSharding path entirely [2], forcing users toward the safer NamedSharding API instead of silently ignoring unsafe configurations during Shardy import. The JAX scipy special module gained Dawson's integral [3], adding another scientific computing primitive to the ecosystem. Across the cloud side, Google Cloud Python is deprecating the experimental Spanner host parameter [4] in favor of a unified `instance_type` option that explicitly marks connections as cloud or omni, cleaning up years of half-finished API surface. The sqlalchemy-spanner package received substantial nox session work [5], standardizing test infrastructure against google-cloud practices. Code generation caught up with grafeas [6] and container analysis [7] libraries, keeping protos in sync with their service definitions.

Action items

→ Audit JAX compilation cache usage for Manual HloSharding patterns before next training run google/jax [immediate]
→ Replace any experimental_host Spanner parameters with instance_type before migration windows googleapis/google-cloud-python [plan]
→ Review JAX NamedSharding documentation for safe distributed sharding patterns google/jax [plan]
→ Monitor sqlalchemy-spanner test suite during next nox run googleapis/google-cloud-python [monitor]

References

[1] Make warnings about security on the compilation cache warnings. google/jax
[2] Remove setting `Manual` HloSharding directly as it would be anyways ignored during Shardy import. If required, JAX NamedSharding should be set instead which would be correctly lowered to corresponding google/jax
[3] scipy.special: add dawsn (Dawson's integral) ↗ google/jax
[4] chore(spanner): deprecate experimental host option/parameter to replace with Spanner Omni (#17246) googleapis/google-cloud-python
[5] chore: add missing nox sessions and polish dependencies in sqlalchemy-spanner ↗ googleapis/google-cloud-python
[6] chore: generate grafeas ↗ googleapis/google-cloud-python
[7] chore: generate google-cloud-containeranalysis ↗ googleapis/google-cloud-python

Quick answers

What shipped in Google on May 30, 2026?: JAX shipped critical warnings for unsafe compilation cache practices, forcing a breaking change in how you specify distributed sharding across the stack. In total, 43 commits, 36 pull requests, and 1 releases landed.
Who contributed to Google on May 30, 2026?: 3 developers shipped this update, including TheSkyentist, chalmerlowe, and parthea.
What were the notable Google updates?: Make warnings about security on the compilation cache warnings, Remove setting `Manual` HloSharding directly as it would be anyways ignored during Shardy import. If required, JAX NamedSharding should be set instead which would be correctly lowered to corresponding, and scipy.special: add dawsn (Dawson's integral).

JAX FIXES REMAT3 CONSTANT HANDLING CRASH, GOOGLE CLOUD PYTHON CENTRALIZES REST TRANSCODING

Matthew Johnson patched a critical remat3 regression where closed-over constants were silently dropped, causing immediate crashes in production rematerialization pipelines [ref:1].

ai 50 shipped 1-min read

Google 1 day ago

JAX TIGHTENS XLA OPTIMIZATION CONTROLS, GOOGLE CLOUD PYTHON SETS UP FEATURE GATES

JAX makes XLA optimization levels human-readable while Google Cloud Python client libraries prepare a unified feature gating system for observability.

ai 54 shipped 1-min read

Google 2 days ago

GENAI AUDIO TRANSCRIPTION SHIPS, PROTO-PLUS FIXES RACE CONDITIONS

Google's AI SDK gains native audio processing while the core Python cloud libraries ship critical stability fixes across the stack.

ai 60 shipped 1-min read

Google 3 days ago

JAX CUTS ASYNC COLLECTIVE PRIMITIVES, GENAI SDK ADDS LIVE API VOCABULARY

JAX is simplifying its async collective operations while the Python GenAI SDK ships custom vocabulary support for the Live API, marking a shift toward leaner abstractions and richer real-time capabilities.

ai 100 shipped 1-min read

Elsewhere on the wire

AI Agents about 9 hours ago

CLAUDE OPUS 5 LANDS ACROSS THE STACK

The newest Anthropic model is now live in langchain, Cline, and llama-index, with native support for extended reasoning and 1M context windows.

ai-agents 28 shipped 1-min read

Local LLMs about 9 hours ago

OLLAMA LANDS LAGUNA SUPPORT AND CRUSHES MEMORY LEAKS WHILE SGLANG HITS V0.5.16 WITH CONFIDENCE-DRIVEN SPECULATIVE DECODING

Ollama shipped three critical performance and reliability fixes for Metal residency and concurrent access patterns, while SGL-Lang released 0.5.16 with a new speculative algorithm hitting 383.7 tok/s on DeepSeek-V4.