ci(release): move :latest to the highest pre-release while no stable release exists

Only pre-releases (v0.1.0-rc.1, rc.2) are published, and :latest followed the highest stable release only, so the
Unraid template and the compose file, which pull :latest, found no image while :nightly was pushed every night.

The new Chronos.Tools command release-channels reads the published releases (stable and pre-releases), ignores drafts
and tags that are not SemVer, counts the tag itself as published and compares by SemVer 2.0 precedence. It prints
latest (the public releases repository: highest stable release only) and image_latest (:latest: the highest stable
release, or the highest pre-release while none is stable). Re-publishing an older tag never rolls either back.
release.yml uses it in place of curl|grep|sort -V; the image job pushes :latest on image_latest. README, the public
README, the compose file and ARCHITECTURE explain :latest, :<version> and :nightly.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Alby96andClaude Opus 5.5 committed 2026-10-26 21:45:57 +01:00
1 parent 5209579631
commit 3679e80ebb
8 files changed
+343 -31

No files matched your search

+2
View File
@@ -3,6 +3,8 @@ name: chronos
services:
chronos:
# :latest is the newest stable release (before the first one, the newest pre-release); :<version> pins a release;
# :nightly is the development version rebuilt every night, not for production.
# While the organisation on Gitea is private, sign in before pulling: docker login gitea.encke-hake.ts.net
image: gitea.encke-hake.ts.net/balbosoft/chronos-server:latest
restart: unless-stopped