ChromeOS releases will soon skip odd numbers to keep up with Chrome updates

For years, the Chrome browser and ChromeOS have moved lockstep in their version numbering. When Chrome 148 arrived, for instance, ChromeOS 148 followed right behind it.

But a major structural change is on the horizon. According to the newly published Chrome Enterprise and Education release notes, Google is officially changing how it numbers future ChromeOS releases. And starting with the deployment of ChromeOS 154, the operating system will begin skipping milestone numbers, incrementing by two versions at a time instead of one.

The two-week browser acceleration

To understand why Google is breaking its long-standing version numbering system, you have to look at a massive shift heading to the desktop browser architecture first. As detailed by Google’s deployment team on the Chrome for Developers Blog, the standard Google Chrome browser (across Desktop, Android, and iOS) is officially moving to a two-week release cycle starting in September 2026 with the launch of Chrome 153.

This cuts the current four-week release cadence exactly in half to ensure developers and consumers get immediate access to new security patches, web platform capabilities, and performance fixes. Because the browser is accelerating to a bi-weekly cadence, it will naturally burn through version numbers twice as fast as it used to.

Keeping the platforms aligned

This introduces a clear logistics problem for ChromeOS. While the browser can easily ship smaller code updates every 14 days, a full desktop operating system requires a much more hardware-level regression checking, OEM validation, and regression stability testing. Because of those physical constraints, ChromeOS will maintain its current 4-week release cadence.

To prevent the browser version numbers from completely pulling away from the operating system version numbers, Google is adjusting the numbering math. Every 4 weeks, when a new stable build of ChromeOS drops, the version number will leap forward by two milestones (e.g., jumping from 152 straight to 154) to perfectly align with whatever version of the Chrome browser is shipping at that exact moment.

What this means for enterprise and LTS channels

If you manage a business or school domain, this change won’t disrupt your operational cadence. Since the actual release frequency for standard ChromeOS updates remains anchored to a 4-week tempo, your deployment schedules and update policies will function exactly as they do today.

For administrators utilizing the Long-term Support (LTS) channel, the actual duration between major platform updates isn’t changing either; LTS builds will continue to deploy every 6 months. However, to stay synchronized with the new numbering system under the hood, the version numbers for LTS channels will now increment by 12 milestones at a time rather than the traditional 6.

It’s a clever bit of version-number gymnastics that will allow ChromeOS to maintain its stable 4-week testing schedule while ensuring the browser it ships with to stay perfectly matched with the rest of the desktop Chrome ecosytem.