230 security fixes is the Important line, not Stable Channel Update

So Chrome Releases put "Stable Channel Update for Desktop" on the feed overnight. Same row on chromium-releases. We flagged it Important as security. The title is kind of the decoy. The line that matters is 230 security fixes, and Chrome 153 is now stable for Windows, Mac, and Linux.

Recency wants the cheerful opener. The Chrome team is delighted, the build rolls out over days or weeks, watch for upcoming feature blogs. Fine. That is what people screenshot. The partner-break line, to the best of my understanding, is the security section: this update includes 230 security fixes. Critical WebGL issues show up early in the list. Google also says it is aware an exploit for CVE-2026-87491 exists in the wild. That is not a feature post. That is a patch-now sentence dressed as a channel note.

I keep almost filing Chrome under "browser bump, ignore." Kind of the wrong habit when you sell next to endpoint, browser security, or anyone who asks whether the fleet is on current stable. Your AE forwards 153.0.8010.36 (Linux) or 153.0.8010.36/.37 on Windows and Mac. Security and compliance people ask about the CVE count and the in-the-wild note. Android got its own Chrome for Android Update in the same window, same Important security flag on the catalog.

Let's say the talking point is not "153 is stable." It is 230 fixes, then CVE-2026-87491 has an exploit in the wild, then yes the channel title still says Stable Channel Update. We pull it into a uniform entry shape at /sources/chrome-releases. Same JSON as everything else. Recency still wants the delighted announcement. Recency is not the patch list.