The Wire · Showcase
JAX CI BROKEN BY PYTHON 3.13 VERSION STRING PARSING
By RepoJournal · Filed · About Google
JAX's build scripts are crashing on Python 3.13-ft to 3.13t conversions, and the fix is live now.
The JAX team deployed a defensive patch [1] that stops the version string conversion from tanking CI pipelines when Python 3.13-ft gets parsed as 3.13t. This isn't a permanent solution - the long-term play is to standardize on 3.13t everywhere - but it unblocks your builds immediately. In parallel, the team updated XLA dependencies [2] to the latest revision, so you're pulling in the latest upstream optimizations alongside the CI fix. No breaking changes here, just infrastructure stabilization.
Action items
- → Sync JAX if you hit Python 3.13 version parsing errors in CI google/jax [immediate]
- → Monitor for the future 3.13t standardization - plan your version string handling now google/jax [plan]
References
- [1] Be more defensive when converting 3.13-ft to 3.13t in build scripts. ↗ google/jax
- [2] Update XLA dependency to use revision http://github.com/openxla/xla/commit/0e07f95f1e0a0bda4fff52de21ecb9e6d32cbe74 google/jax
FAQ
- What changed in Google on June 15, 2026?
- JAX's build scripts are crashing on Python 3.13-ft to 3.13t conversions, and the fix is live now.
- What should Google teams do about it?
- Sync JAX if you hit Python 3.13 version parsing errors in CI • Monitor for the future 3.13t standardization - plan your version string handling now
- Which Google repositories shipped on June 15, 2026?
- google/jax