ChromeOS 152 started reaching the Stable channel on September 8, and most of what it does happens without asking for your attention. The two changes worth knowing about are a smarter way installed web apps handle links, and a security upgrade that’s less about today’s problems than the ones a decade out.
PWA links stop dumping you in a browser tab
Before ChromeOS 152, clicking a link tied to an app you’d installed as a Progressive Web App (a project board, a media service, a work tool) usually opened a new browser tab anyway, unless you’d already dug into that app’s settings and turned link capturing on by hand. ChromeOS 152 makes that behavior the default for every installed PWA. Click a matching link now and it opens straight into that app’s own window instead of a tab you’ll have to close later. It’s a small fix, but it’s exactly the kind of friction that made installed web apps feel like a workaround instead of a real app. If you haven’t tried installing a site as an app yet, our guide to installing PWAs on a Chromebook walks through it.
ChromeOS 152 also adds native support for Google’s Certificate Authority Connector, letting Google Cloud issue and validate custom enterprise certificates on ChromeOS without routing through a third-party proxy. That’s an IT admin feature, not something most home users will ever touch, but it closes a gap that Windows, Mac, and Linux have had for a while.
A quantum-safe upgrade you’ll never see
The more consequential change in ChromeOS 152 is invisible. Google has started moving how it signs updates to browser components and extensions away from classical ECDSA signatures and toward post-quantum cryptography. Your desktop won’t look any different. What’s different is the math protecting those background updates from a threat that doesn’t exist yet: a future quantum computer powerful enough to break today’s encryption and, in theory, decrypt data or forge signatures captured years earlier. It’s what security folks call “harvest now, decrypt later”: scoop up the encrypted data now, crack it later once a quantum computer can. That’s why the switch is happening well before quantum computers are actually a threat, not after. For more on how ChromeOS handles security day to day, see our breakdown of Chromebook security features.
Why ChromeOS 154 will look like it skipped a number
One detail buried in the release notes explains a change you’ll notice later this year. Chrome’s desktop browser just switched to a two-week release cycle, and that faster pace has started pulling the browser’s version number ahead of ChromeOS’s own. To keep the two roughly aligned, Google confirmed that starting with ChromeOS 154, the platform’s version number will jump by two instead of one at each release. The actual release schedule isn’t changing: ChromeOS still ships a new milestone roughly every four weeks, and Long Term Support builds still land every six months. They’ll just carry version numbers that jump by 12 instead of 1 each cycle. If ChromeOS ever appears to skip straight from 153 to 156 on your device, that’s bookkeeping, not a missed update.
What Chromebook owners should do
Nothing urgent, but it’s worth a quick check. Open Settings, click About ChromeOS in the lower-left menu, then Check for updates. Most boards were already receiving version 16765.41.0 this week; a handful of models, including the Lenovo Chromebook Plus 14 and Acer Chromebook Plus Spin 514, have tended to trail the main rollout by a day or two in past releases, so don’t worry if it hasn’t shown up yet. If a download ever stalls partway through, our guide to updating ChromeOS manually covers the fixes that usually clear it.
