A shorter gap between milestones
Chrome 154 entered the desktop stable channel on September 22, two weeks after the planned start of Google’s shorter milestone schedule with Chrome 153. Google says the Windows, Mac and Linux rollout will take place over days or weeks; the release announcement does not mean every device has already updated.
Google says the shorter schedule applies to beta and stable releases on desktop, Android and iOS. Dev and Canary keep their existing cadence. Extended Stable remains on an eight-week cycle for organisations that need more time between major changes, while Chromebook releases depend on separate platform testing.
Security updates are a separate cadence
Major version numbers and security patches follow different timetables. Google’s July security update describes weekly fixes alongside the two-week milestone transition, and a pilot of two security releases per week. A pilot is not a promise that every device or channel already receives that frequency.
Google also describes greater use of AI in finding, assessing and fixing vulnerabilities. That is the company’s account of its engineering process, not a guarantee that software has become free of exploitable defects. Discovery, a code correction, a released package and an installed update remain separate stages.
The last step is still on the device
For everyday users, keep automatic updates enabled and complete a requested browser restart when practical. A running browser can remain on an older version even after an update is available. On an organisation-managed computer, the administrator may control the applicable release channel and rollout.
For website teams, check upcoming changes in beta and keep testing the browsers your visitors use. For users, the practical check is the installed version and any pending restart, rather than the date on an announcement. Our reporting on EU product-security reporting rules explains a separate part of the process: what manufacturers must report when vulnerabilities or serious incidents arise.