RepoJournal
Google

Google

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

Pick a date

The Wire · Showcase

JAX CLEARS THE DECK: NVSHMEM DEPRECATED, NUMPY 2.0 SUPPORT DROPPED

By RepoJournal · Filed · About Google

JAX is shipping breaking changes across the stack today, starting with mandatory migration away from NVSHMEM to NCCL Device API and dropping support for NumPy 2.0 and SciPy 1.14 in the 0.11.0 release.

The Mosaic GPU team is removing NVSHMEM usage from XLA custom kernels, forcing customers onto NCCL Device API through collective metadata [1]. This is part of a broader cleanup push: JAX is dropping the deprecated public API module jax.cloud_tpu_init [4], removing stale JAX_IFRT_VERSION ifdefs now that minimum version sits at 55 [3], and purging version tests since jaxlib's minimum is now v0.10.2 [2]. The 0.11.0 release is the hard cutoff for NumPy 2.0 and SciPy 1.14 support [5]. Over on the Python Genai side, version 2.9.0-rc1 is in flight [6]. Google Cloud Python is tightening its typing game: Firestore's CollectionReference now properly annotates .document() calls to return DocumentReference types instead of inheriting base collection typing [7], while the full library suite just finished a librarian regeneration cycle to sync config with generated code [8].

Action items

References

  1. [1] [Mosaic:GPU] Remove NVSHMEM usage from Mosaic XLA custom kernel and tests. google/jax
  2. [2] Remove stale version tests now the minimum jaxlib is v0.10.2. google/jax
  3. [3] Remove stale JAX_IFRT_VERSION ifdefs. google/jax
  4. [4] Drop the deprecated public API module jax.cloud_tpu_init. google/jax
  5. [5] Drop support for NumPy 2.0 and SciPy 1.14 for the jax 0.11.0 release. google/jax
  6. [6] Copybara import of the project: googleapis/python-genai
  7. [7] chore(firestore): improve typing for collection (#16999) googleapis/google-cloud-python
  8. [8] chore: re-generate all (#17505) googleapis/google-cloud-python

FAQ

What changed in Google on June 19, 2026?
JAX is shipping breaking changes across the stack today, starting with mandatory migration away from NVSHMEM to NCCL Device API and dropping support for NumPy 2.0 and SciPy 1.14 in the 0.11.0 release.
What should Google teams do about it?
If you're on Mosaic GPU, audit custom kernels for NVSHMEM usage and migrate to NCCL Device API before JAX 0.11.0 • Drop NumPy 2.0 and SciPy 1.14 from your dependency matrices before JAX 0.11.0 release • Update any code calling jax.cloud_tpu_init - it's being removed
Which Google repositories shipped on June 19, 2026?
google/jax, googleapis/python-genai, googleapis/google-cloud-python

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • 14 famous open source orgs
  • One wire per day
  • Public, generic
  • Read on the web, when you remember

Your wire

  • Up to 1,500 of your repos - orgs, deps, vendors
  • Morning and evening briefs
  • Action items routed to your team
  • Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.