selfupgrade is the Important line in Grav, not 2.1.2

So Grav CMS put three Important breaking-change rows on the feed within about an hour: 2.0.27, 2.1.1, and 2.1.2. Recency wants the newest tag. Fine. The line that matters, to the best of my understanding, is that Grav 2.0 sites can now self-upgrade to 2.1. bin/gpm selfupgrade no longer incorrectly reports 2.0 sites as up-to-date, and the update check no longer incorrectly flags minor releases as major. Admin2 updates from 2.0 to 2.1 now succeed.

I keep almost filing patch clusters under "CMS bump spam, ignore." Kind of the wrong habit when a customer on 2.0 has been staring at an up-to-date signal while 2.1 sat one line away. Let's say the talking point is not "2.1.2 shipped." It is the upgrade path stopped lying. Same day, same source, three Important flags pointing at one operational break. If you only scan titles, you get three version bumps. If you read the Important reasons, you get one partner-break story repeated until the tooling catches up.

There is a fourth Important row in the same window if you sell into AI-agent tooling. Grav 2.1.0 says pages can now be read as Markdown for AI agents, with text clients getting content as Markdown and skipping navigation and footers. That is a product change your AE will screenshot. Still secondary to the selfupgrade story if you are in a CMS renewal and the customer asks why selfupgrade kept saying they were done.

We pull it into a uniform entry shape at /sources/grav-releases. Same JSON as everything else. The talking point is selfupgrade no longer calls 2.0 current, then Admin2 can climb 2.0 to 2.1, then yes 2.1.0 also has Markdown for agents. Recency still wants 2.1.2. Recency is not the selfupgrade fix.