The Wire · Showcase
JAX REVERTS BREAKING CHANGE, SYNCS XLA UPSTREAM
By RepoJournal · Filed · About Google
A changelist that hit production got rolled back twice in 12 hours, signaling either a critical regression or a coordination miss that JAX caught before it spread.
The JAX team reverted changelist 961233365 not once but twice, with copybara-service and Jinliang Wei both rolling back the same commit [1][2]. The identical reverts of 57df5685 suggest this wasn't a merge conflict or stale code, but a deliberate decision to kill something that landed. Simultaneously, the team pulled in a fresh XLA dependency pointing to upstream revision 7c3dd19 [3], which hints the problem may have been a version mismatch or an XLA API shift that broke on import. With only 2 commits and 1 PR across the period, this is focused work: undo what broke, sync what matters, move on.
One email a day. Unsubscribe in one click.
Keep up with Google in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.
One email a day. Unsubscribe in one click. Read a past issue →
Action items
- → Pull latest JAX if you're on a development branch - the revert is already live google/jax [plan]
- → Watch for XLA API changes in the next JAX release notes google/jax [monitor]
References
- [1] rollback of changelist 961233365. ↗ google/jax
- [2] rollback of changelist 961233365. google/jax
- [3] Update XLA dependency to use revision google/jax