Chrome 153 Starts Google's Two Week Release Cycle

Chrome 153 shipped on 8 September and started something bigger than the usual version bump: Google's new two week release cycle. Chrome has run on a four week cadence for years. From this release on, stable updates land roughly every fortnight, which means smaller changes per release and a shorter wait for anything that missed the last train.

The release itself carries a handful of features worth a developer's attention. scroll-axis-lock is a new CSS property that lets a page opt out of the browser's habit of locking a scroll gesture to one axis, useful for anything meant to scroll diagonally, like a map or a canvas. Chrome 153 also introduces dedicated camera and microphone HTML elements, giving pages a semantic, single purpose way to request one media permission at a time instead of the broader user media prompt. Under the bonnet, Chrome swapped in a Rust based XML parser aimed at closing a long standing class of memory safety bugs.

Faster release cycles are a trade off, not a pure win. Smaller, more frequent updates mean less time for any single change to bake before it reaches billions of users, and QA teams that test against specific Chrome versions now have twice as many versions a year to track. Firefox made a similar move to two week releases a few weeks earlier, so this is now the direction both major non Safari engines are heading, and it puts pressure on Safari to either follow or explain why a slower, steadier cadence is the better trade off for its own users.

For studios like ours, the practical effect is boring but real: fewer surprises held back for a big quarterly release, more small features arriving as soon as they are ready. scroll-axis-lock in particular is one we will use the next time a client wants a horizontally scrolling gallery that does not fight the user's thumb.