Most users need no action is the Important line you skip

So Heroku Platform Updates put Heroku-22, Heroku-24 and Heroku-26 stacks updated on the feed last night. We flagged it Important as security. The sentence that matters is not the calm opener. Most users need no action. That's the line that makes an AE stop reading. The next clause is the one: container stack users must rebuild their Docker images.

I keep treating "no action" like a skip. Kind of the wrong habit for partner ops. We already wrote about security clusters when several vendors ship real patches the same night. This is a different miss. The Important feed is full of SolidJS release candidates and Apollo RCs that look like breaking changes. Recency wants those. The Heroku row looks boring on purpose.

To the best of my understanding this is the split-audience note. Same stack names show up on heroku-updates, heroku-platform-updates, and heroku-cli-updates. Same story three times. Most of the install base can ignore it. The container cohort cannot. If you sell next to Heroku, or your customer runs the container stack, let's say, that rebuild is the talking point for the week. Not "Heroku did a security update."

I almost filed this under last week's security-cluster teaching. Different lesson. Cluster is when the patch list is the point. This is one vendor telling most people to relax while a smaller group has work to do. Miss the second half and you tell the wrong customer they're fine.

The Important flag caught the rebuild cohort. Recency still wants you looking at Next.js canaries. Fine. Recency is not the container rebuild.

We pull it into a uniform entry shape at /sources/heroku-platform-updates. Same JSON as everything else. The talking point is container stack users must rebuild. Most users need no action is the decoy.