jcoffey-dev
dfff9c7cdf
A 2026.x release from this branch moved :latest, GHCR's :latest and the GitHub "latest release" on every tag. That is right while 2026.x is the newest series, and wrong once 27.1 ships: a 2026.x security release after it would take :latest back to the older line. The version job now asks Gitea for the newest final releases and moves :latest only while none is numbered by series (v27.1, v27.1.3), so the switch happens on its own when 27.1 is published, with nothing to change on release day. The release body says which way it went. The check fails rather than guess: a wrong :latest is worse than a re-run. Checked against the live API (no series release yet, :latest moves) and against a list with v27.1 in it (it holds). Both workflow files parse.