RepoJournal
Google

Google

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

Pick a date

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

The Wire · Showcase

JAX ADDS ONEAPI GPU RUNTIME AS PYTHON 3.14 FORCES GOOGLE-AUTH DEPENDENCY PURGE

By RepoJournal · Filed · About Google

JAX shipped OneAPI (SYCL) GPU support while google-auth spent the night locking down five critical dependencies for Python 3.14 compatibility.

JAX merged OneAPI GPU runtime functions [1], bringing SYCL support to jaxlib with new type aliases and kernel helpers in the oneapi directory. On the compute side, Pallas added a synchronous MMA primitive [2] and cleaned house by removing unused linalg_vectorization code [3]. Meanwhile, google-auth faced a Python 3.14 reckoning: the stdlib dropped pkg_resources, forcing cryptography to jump to 41.0.5+ [8], while urllib3, packaging, aiohttp, and rsa all needed hard version bounds to survive [5] [6] [7] [9]. These aren't minor compatibility tweaks - they're the cost of staying on the standard library's upgrade treadmill. The python-genai SDK cleaned up OpenAPI schema property sorting and added retrieval result steps [4], mostly chore work ahead of larger feature rolls.

Action items

References

  1. [1] [OneAPI GPU] Add OneAPI (SYCL) GPU Runtime Functions. ↗ google/jax
  2. [2] [pallas:mgpu] Added a primitive for synchronous MMA ↗ google/jax
  3. [3] Remove unused linalg_vectorization from mosaic. google/jax
  4. [4] feat: add retrieval result step and new fields to maps and search results ↗ googleapis/python-genai
  5. [5] fix(google-auth): add aiohttp bound for Python 3.14 ↗ googleapis/google-cloud-python
  6. [6] chore(google-auth): fix aiohttp 3.10+ test compatibility ↗ googleapis/google-cloud-python
  7. [7] fix(google-auth): raise rsa extra lower bound to 4.0 (#17652) googleapis/google-cloud-python
  8. [8] fix(google-auth): add cryptography bound for Python 3.14 (#17649) googleapis/google-cloud-python
  9. [9] fix(google-auth): add bounds for urllib3 and packaging dependencies (#17647) googleapis/google-cloud-python

FAQ

What changed in Google on July 8, 2026?
JAX shipped OneAPI (SYCL) GPU support while google-auth spent the night locking down five critical dependencies for Python 3.14 compatibility.
What should Google teams do about it?
Pin google-auth to versions with cryptography >= 41.0.5, rsa >= 4.0.0, urllib3 >= 1.26.15, aiohttp >= 3.9.0 before deploying to Python 3.14 • Test JAX OneAPI runtime in your GPU pipeline if you use SYCL-compatible hardware • Monitor Pallas synchronous MMA primitive adoption for HPC workloads
Which Google repositories shipped on July 8, 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.