The Wire · Showcase
JAX tightens compilation cache security while Google Cloud standardizes Spanner connections
By RepoJournal · Filed · About Google
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
FAQ
- What changed 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.
- What should Google teams do about it?
- Audit JAX compilation cache usage for Manual HloSharding patterns before next training run • Replace any experimental_host Spanner parameters with instance_type before migration windows • Review JAX NamedSharding documentation for safe distributed sharding patterns
- Which Google repositories shipped on May 30, 2026?
- google/jax, googleapis/google-cloud-python