RepoJournal
Google

Google

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

Pick a date

  1. Sun 3 may
  2. Mon 4 may
  3. Tue 5 may
  4. Wed 6 may
  5. Thu 7 may
  6. Fri 8 may
  7. Sat 9 may
  8. Sun 10 may
  9. Mon 11 may
  10. Tue 12 may
  11. Wed 13 may
  12. Fri 15 may
  13. Sat 16 may
  14. Sun 17 may
  15. Mon 18 may
  16. Tue 19 may
  17. Wed 20 may
  18. Thu 21 may
  19. Sat 23 may
  20. Sun 24 may
  21. Mon 25 may
  22. Tue 26 may
  23. Thu 28 may
  24. Fri 29 may
  25. Sat 30 may
  26. Sun 31 may
  27. Mon 1 jun
  28. Mon 8 jun
  29. Tue 9 jun
  30. Today 10 jun

The Wire · Showcase

JAX OVERHAULS SERIALIZATION APIS WHILE GOOGLE CLOUD DROPS PYTHON 3.7 SUPPORT

By RepoJournal · Filed · About Google

JAX's PjRt layer now accepts SDY target versions during serialization, giving you fine-grained control over compatibility across versions.

The big shift on the JAX desk: SDY dialect target versioning is live [1]. Serialize() and SerializeUsingVersionedStablehlo() now accept an explicit SDY target version parameter, with GetDefaultSdyVersion() providing sensible defaults (following the same 12-week deprecation window as StableHlo). This matters because it lets you version-lock your compiled kernels independent of your JAX runtime. Meanwhile, JAX added the Faddeeva function (wofz) and extended erfcx to handle complex inputs [2], rounding out the scipy.special family. Shape polymorphism now has partial support for ragged_dot [3], though modes 1 and 2 still bail on dynamic group sizes (error messages now in place). The OneAPI GPU plugin skeleton landed [4], setting up Intel SYCL infrastructure with no kernel implementations yet, so don't expect GPU compute from this one. On the Google Cloud front, google-cloud-logging is cutting Python 3.7, 3.8, and 3.9 support [5], consolidating on 3.10+ and modernizing dependency chains. The gapic-generator shipped two releases [6][7] fixing coverage pragmas and URL routing in setup.py. Python-genai expanded computer_use field support for Vertex [8]. One test suite fix resolved a protobuf unpacking issue in BigTable admin tests [9].

Action items

References

  1. [1] [SDY] Update PjRt MLIR/HLO conversion APIs to accept a SDY target version during serialization google/jax
  2. [2] add wofz (Faddeeva function) and extend erfcx to complex inputs ↗ google/jax
  3. [3] [shape_poly] Add partial support for lax.ragged_dot. ↗ google/jax
  4. [4] [OneAPI GPU] Add OneAPI plugin extension infrastructure and glue code ↗ google/jax
  5. [5] feat(logging): drop support for Python 3.7, 3.8, and 3.9 runtimes (#17276) googleapis/google-cloud-python
  6. [6] gapic-generator: v1.34.1 ↗ googleapis/google-cloud-python
  7. [7] gapic-generator: v1.34.0 ↗ googleapis/google-cloud-python
  8. [8] feat: additional computer_use field support for vertex. ↗ googleapis/python-genai
  9. [9] tests: resolve failure related to unpacking dictionary for protobuf messages ↗ googleapis/google-cloud-python

FAQ

What changed in Google on May 28, 2026?
JAX's PjRt layer now accepts SDY target versions during serialization, giving you fine-grained control over compatibility across versions.
What should Google teams do about it?
If you're on Python 3.9 with google-cloud-logging, plan your 3.10+ migration now • Review JAX's new SDY target versioning if you're serializing compiled graphs • Update shape polymorphism code paths to avoid ragged_dot with dynamic group sizes
Which Google repositories shipped on May 28, 2026?
google/jax, googleapis/google-cloud-python, googleapis/python-genai

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.