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:
1 parent
5209579631
commit
3679e80ebb
8 files changed
+343
-31
No files matched your search
@@ -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
|
||||
|
||||
@@ -74,9 +74,10 @@ Open `http://<host>:8080/admin`, sign in as `admin` with the password from `.env
|
||||
clients connect to `https://<host>:8443`; the first connection shows the server's certificate fingerprint, which the
|
||||
admin panel shows under Settings so you can compare them.
|
||||
|
||||
- Image: `gitea.encke-hake.ts.net/balbosoft/chronos-server:latest` (also `:<version>`; `:nightly` follows development
|
||||
and is not for production use; pre-releases have no `:latest`). Architecture: `linux/amd64`. If the registry asks you
|
||||
to sign in, run `docker login gitea.encke-hake.ts.net` with your Gitea account first.
|
||||
- Image: `gitea.encke-hake.ts.net/balbosoft/chronos-server:latest`, the newest stable release (before the first one,
|
||||
the newest pre-release); also `:<version>`, and `:nightly`, the development version rebuilt every night, not for
|
||||
production use. Architecture: `linux/amd64`. If the registry asks you to sign in, run
|
||||
`docker login gitea.encke-hake.ts.net` with your Gitea account first.
|
||||
- Volumes: `/archive` (originals, sidecars, proxies, renders — the archive stays readable without Chronos) and `/data`
|
||||
(settings, TLS certificate, uploads in progress, logs).
|
||||
- Upgrade: `docker compose pull && docker compose up -d`. Jobs in progress resume from their last checkpoint.
|
||||
|
||||
Reference in new issue
Block a user