A dated 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 security release from this
branch would take :latest back to the older line.
Both CIs now ask Gitea for the newest final releases and move :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. The check fails rather than guess. The
inherited v1.0.x numbers don't count as a series.
jcoffey-dev
a022ce4d2b