Chrome 155 shipped right on schedule — it took two weeks to reach half of desktop Chrome
Chrome 155 hit stable on Oct 6, 2026 — the exact date our pipeline called 99 days out. It took 6% of desktop Chrome traffic in week one and 51% two weeks later.
Chrome 155 reached the stable channel on October 6, 2026. I knew that on June 29: my forecast pipeline pulled the date from Google's own machine-readable release calendar, logged it with high confidence, and Chrome hit it to the day — 99 days later, with no slip, no drama and no news cycle.
Boring? That's kind of the point. In an ecosystem where store policies shift overnight and APIs ride milestones without a release note, the Chrome release train is one of the few clocks an extension developer can set a watch by. But there's a second clock — when your users actually get the new version — and that one keeps its own schedule. In the week 155 "shipped", it carried about 6% of desktop Chrome traffic. Two weeks later it carried half. It never got higher than that, and about 40% of that traffic stayed on older versions the whole time.
And this train carries the whole store. Our catalog tracks 325,359 Chrome Web Store listings with a combined ~2.47 billion store-reported users. Every couple of weeks, all of them wake up inside a new browser build, whether they asked for it or not.
So here's the retrospective of a non-event: what the schedule promised, what it delivered, and the part nobody schedules.
The forecast that came true
On June 29, the pipeline logged a signal for the Chrome 155 release schedule, sourced from the Chromium Dash milestone schedule — Google publishes the whole release calendar as machine-readable JSON, months ahead. The dates I wrote down then:
- Branch point: September 14 — code freeze; the last day a feature targeting 155 could merge upstream.
- Earliest beta: September 16.
- Final beta: September 23.
- Stable: October 6.
All four held. Stable landed on the scheduled day, and the train kept rolling on the same roughly two-week cadence around it: Chrome 154 went stable on September 22, Chrome 156 followed 155 on October 20, and Chrome 157 — the current stable as of November 9 — landed November 3. Chromium Dash has Chrome 158 scheduled for November 17 (154, 156, 157, 158).
That predictability splits into two audiences. If you're among the few committing to Chromium upstream, the branch point is the only hard deadline there is — miss the freeze and your change waits for the next train. That's exactly what happened to runtime.onExtensionLoaded: committed September 30, two days after Chrome 156 branched, so its first stable was 157 (the full story is here).
If you ship extensions but don't commit to Chromium — nearly everyone — the stable date answers a different question: when can I start relying on what this milestone brought? And that's where the second clock takes over.
The clock nobody schedules
A stable date is when a version starts shipping. It is not when your users get it. StatCounter's weekly browser-version data for desktop, worldwide, shows the ramp. Each number is Chrome 155's share of desktop Chrome page views:
- Release week (October 5–11): about 6%. Chrome 154 still carried about 42%.
- One week later: about 45%.
- Two weeks later: about 51% — the peak. Chrome 156 went stable that week, on October 20.
- Three weeks later: about 17%, with Chrome 156 already at about 44%.
- Five weeks later (November 9–15): under 2%.
So the middle of the curve is fast. About half of desktop Chrome traffic moved to 155 within two weeks — and on a two-week release cadence, that's exactly when the next version starts replacing it. 155 peaked at about 51% and never went higher.
The tail is the slow part. Add up Chrome 155 and everything newer, and the share reaches about 60% two weeks after release — then stops climbing. Through mid-November, roughly 40% of desktop Chrome page views still came from versions older than 155. Chrome 151, stable since July 28, held between 4% and 11% depending on the week. About a fifth of the traffic came from versions older than Chrome 148, which went stable on May 5.
Chrome's numbered versions add up to roughly 65% of all desktop page views in the same data, so these shares aren't a niche concern. Two caveats: StatCounter counts page views, not people, and this is desktop only.
None of this is a malfunction. Chrome rolls stable out gradually, managed fleets pin versions for months, and plenty of people simply don't restart their browser. I watched this up close with 155's own headline API: runtime.onEnabled shipped in the milestone, and in release week only about 6% of desktop Chrome traffic came from a browser that could fire it — which is why every code sample in that post feature-detects (chrome.runtime.onEnabled?.addListener(...)) instead of sniffing versions.
The lesson I keep relearning: a milestone's stable date tells you when a feature starts reaching users. It never tells you when you can assume them. If you're waiting on 157's runtime.onExtensionLoaded: 157 went stable on November 3, carried about 7% of desktop Chrome traffic that week and about 40% the week after. The bulk shows up within two weeks. The rest takes months.
What the train carries
Scale, with the fine print. The 325,359 figure counts Chrome Web Store listings our catalog tracks, including the 44,444 (a combined ~280M store-reported users) that were already unavailable in the store at our last check. The user figure — ~2.47 billion — sums each listing's store-reported count, so it is not unique people: one person with five extensions counts five times. And the count checks nothing beyond "it's a Chrome Web Store listing" — no manifest version, no API usage, no code — so treat it as the size of the population riding this train, not as the number of listings any given milestone changes.
That population includes Adobe Acrobat, Google Translate, Grammarly, uBlock Origin Lite, Adblock Plus, AdGuard, Chrome Remote Desktop, NordVPN, PayPal Honey and Claude — and they ride the same train as every other listing in the ~325k we track. Most milestones change nothing for most of them. Some aren't that quiet: 155 itself carried runtime.onEnabled past nearly everyone, and 154 brought MV3 an opt-in fix for events lost to async listener registration. The train is predictable; what rides it isn't always.
What to do now
- Feature-detect, never version-sniff. With roughly 40% of desktop Chrome traffic still below 155 five weeks after its release, and a tail that runs for months,
if (chrome.runtime.onEnabled)beats any parsing of the user-agent string. - Plan against the branch point, not the stable date. The Chromium Dash schedule is machine-readable and lands months out. Upstream contributors: the branch point is your deadline. Everyone else: beta opens at the earliest two days later — that's your integration-testing window, the same advice my June signal record gave.
- Check your code against the changes we track. The train outruns anyone's changelog reading:
npx @extenshi/cli@latest advise .matches your extension against every browser change in our catalog and prints the file and line of each hit — local, no account, no API key. For a full pre-upload security scan,@extenshi/cliruns 3 scans + 10 reads free, one-time, with a free account; prepaid credit packs cover you past that. - Keep an eye on where your listing sits — manifest version, permissions and store status are one search away in the catalog. A good share of your users' browsers will keep lagging the release notes for months either way.
See where your extension stands in the catalog → — manifest version, permissions and store status on Chrome, Firefox and Edge.
Sources
- Chrome 155 milestone schedule — Chromium Dash (Google); also 154, 156, 157, 158
- Desktop browser version market share worldwide, weekly, weeks 41–46 of 2026 — StatCounter Global Stats
- runtime.onEnabled shipped in Chrome 155, onExtensionLoaded is next — extenshi.io blog
- Chrome 154's async-listener registration change — extenshi.io blog
Catalog numbers come from Extenshi's scans of Chrome Web Store listings and their store-reported user counts, as of November 2026; the count includes listings already unavailable in their store, and figures shift as we re-scan. Adoption percentages are each Chrome version's share of desktop Chrome page views, worked out from StatCounter Global Stats weekly browser-version data (desktop, worldwide; each numbered Chrome version divided by the sum of all numbered Chrome versions), read on November 18, 2026. They measure page views, not people, and StatCounter can revise them. Release dates come from Chromium Dash; the dates already passed held, and November 17 for Chrome 158 was still a scheduled date when this post went up on November 9. Extenshi does not independently verify all claims made by third parties, and references to specific extensions reflect their size in our catalog, not accusations of wrongdoing. If you believe any information is inaccurate, please contact us at [email protected].
Correction, November 18, 2026: an earlier version of this post, title included, said that five weeks after release only about 25% of Chrome users were on Chrome 155 and that Chrome 157 sat at 0.11%. Those figures came from Can I Use's usage table, which is a lagging monthly average, not current adoption. The adoption section now uses StatCounter's weekly data: about 6% of desktop Chrome page views in release week and about 51% two weeks later. The title and description changed with it. A link to a forecast record in a repository readers can't open was removed.
Related Articles

runtime.onEnabled shipped in Chrome 155, onExtensionLoaded is next: how to wire both
Chrome 155 added runtime.onEnabled; runtime.onExtensionLoaded follows in 157. Which event fires when, one listener pattern for both, and the edge cases.

Chrome 154 landed MV3's lost-event fix — for up to 276,820 Chrome extensions that can't use it yet
Chrome 154 shipped the async_listener_registration manifest key for MV3 service workers. Here's what landed, who it covers, and why you shouldn't switch yet.

Safari 27's four web extension upgrades — and our forecast missed them
Safari 27 web extensions get runtime.getDocumentId(), user-gesture propagation, a tabId for windows.create and error reporting. What landed, what to do.

We counted what Chrome's Manifest V2 sunset actually removed — and it wasn't the ad blockers
Everyone said Chrome's Manifest V2 deadline would kill ad blockers. Here's what the sunset actually stranded — and why Firefox is now the MV2 refuge.