TechCrunch AI · Published 2026-09-08

Chrome moves major releases to two weeks; security patches have their own cadence

Starting with Chrome 153, major releases move from every four weeks to every two. Security patches also have their own cadence, and restarting remains an important step in applying downloaded updates.

The Google Chrome app icon on a smartphone screen
Image: TechCrunch · source article image · Open full-size image

中文

Two-week milestones, separate security updates

TechCrunch reports that Chrome 153, released September 8 on desktop, iOS and Android, begins the two-week milestone schedule. Features and completed changes can reach Stable sooner than under the four-week cadence.

Google’s security explanation distinguishes major milestones from weekly security updates and a pilot of two security releases per week. A two-week milestone cycle does not mean security fixes must wait for the next major version.

Major releases: 4 → 2 weeks
BitShovel diagram · based on the sources retained for this article. · Open full-size image

中文

From public code to the running browser

Once a fix is visible in public code, attackers may examine the change too. Google aims to shorten the gap between a landed fix and protection on users’ machines.

Chrome prepares updates in the background and generally applies them at restart. Google is researching dynamic patching and smoother session restoration; that does not establish that every device already updates without restarting.

Important additions and corrections

Dates below mark changes to our coverage.

  • Correction ·

    Distinguished two-week milestones from more frequent security patches and the usual restart step.

Sources and notes

sources中文

Sources and notes

Retained summary and context

Read claims in the context of the original page. Claims remain attributed to their sources. Collection is not proof of the claims or practical outcomes.

Sources and evidence · 2 links

Each link has a purpose and scope. Link counts do not establish independent confirmation; direct support applies only to the statements specified below.

This page keeps the original link and a short account. Follow the links below for the publisher’s full explanation.

Source timeline
  1. · Found this reading link via TechCrunch AI.
Collection record

First discovered: ; added to the library:

Collection and source publication have distinct dates.

Editorial record

Corrected

· Beijing time (UTC+8)

Distinguished two-week milestones from more frequent security patches and the usual restart step. Original event, discovery and collection dates remain.

Sources and full record

This dates our review of the wording and sources, not a project release or product update.

Full record: before, after and sources (JSON)

Corrections and feedback