CI: leave :latest to the newest series once 27.1 ships (release/2026) #240

Merged

jcoffey-dev merged 1 commits from ci/latest-follows-the-newest-series into release/2026

2026-10-29 19:02:59 +00:00

Author	SHA1	Message	Date
jcoffey-dev	dfff9c7cdf	CI: leave :latest to the newest series once 27.1 ships ci / fork-checks (pull_request) Skipped Details ci / build (pull_request) Skipped Details github/ci (branch) GitHub Actions Details ci / github (pull_request) Successful in 8m25s Details 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.	2026-10-29 11:53:28 -07:00

Author

SHA1

Message

Date

jcoffey-dev

dfff9c7cdf

CI: leave :latest to the newest series once 27.1 ships

ci / fork-checks (pull_request) Skipped

Details

ci / build (pull_request) Skipped

Details

github/ci (branch) GitHub Actions

Details

ci / github (pull_request) Successful in 8m25s

Details

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.

2026-10-29 11:53:28 -07:00