The release step decided :latest and the releases repository's content
after the Gitea release was already public, and could then fail or decide
wrongly (owner review 2, phase 1 review):
- Re-publishing v0.1.0-rc.1 or rc.2 builds Chronos.Tools from the tag,
which has no release-channels: the step failed after publishing and the
image job never ran. Any failure to decide (a tag older than the
command, an unreadable page, a body that is not a list) now warns and
moves no channel, so the version's image is still pushed.
- Only the first page (50, newest first) of releases was read, and
pre-releases now share it with stable ones: 50 pre-releases after a
stable release hid it and moved :latest to a pre-release. The workflow
reads every page up to the first empty one (at most 100) and
release-channels takes one --releases file per page (Args.GetAll).
- The Version step accepted tags release-channels refuses (v01.2.0), which
then failed only after publishing. It now uses release-channels' SemVer
2.0 pattern without +BUILD, and a test keeps the two in step.
BRIEF §19.3, DECISIONS, CHANGELOG and README step 5 say so.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>