7 Commits

Include renames

Author	SHA1	Message	Date
tben	f7ef218507	Take the Gitea registry out of CI and mirror it separately ... The Gitea registry is on a VPN, which a GitHub runner can never reach, so the mirror step in the release workflow could only ever fail: its last four releases reported a step that did nothing. The workflow now builds and pushes to GHCR alone, which is the registry the installer defaults to, and nothing in CI mentions Gitea. The image reaches the Gitea registry through `scripts/mirror-gitea.sh` (`bun run mirror:gitea`) instead, run in parallel with a release and from the VPN side: it copies from the Gitea host over ssh, where skopeo can see both registries, so nothing has to be installed there. `skopeo copy --all` keeps the manifest list and its signatures, and every destination tag is read back and compared with GHCR's digest, so a partial copy fails loudly instead of being assumed to have worked. `latest` and `major.minor` are only moved while that release still owns them in GHCR, so mirroring an older release never rolls them back. Neither direction can fail the other now, which is the point: a registry that is down, slow or full no longer takes a release with it.	2026-10-23 12:03:23 +01:00
tben	796c53716f	Show a mirror failure, and link the release's own range	2026-10-23 06:54:06 +01:00
tben	524f0dde36	Show the running version on Settings > General ... The General page ends with a Version block naming the release this server runs, so an update can be confirmed from the app. The version is COBBLE_VERSION, the release tag the image was built with (Dockerfile ARG, passed by the release workflow, which falls back to package.json's version on a workflow-dispatch build), else package.json's version, which a development server reports too, with (development) after it. runningVersion (src/utils/running-version.ts) drops an unusable version string rather than showing it. Also includes the working tree's pending signup guard in src/pages/__root.server.ts: a user who still holds a session while the install has no users is sent to /auth/logout (and may load it).	2026-10-22 16:03:56 +01:00
tben	06210f00a5	Build the release image once and mirror it to Gitea ... A job-level continue-on-error rejects an expression, and a second registry must not decide whether a release ships.	2026-10-22 14:02:21 +01:00
tben	38221c4baa	Keep secrets out of the release matrix, where Actions rejects them	2026-10-22 13:58:59 +01:00
tben	e45aa4162a	Give each registry its own release leg, so Gitea cannot fail a release ... Cloudflare rate limits git.tben.me's blob uploads (429/1015), which failed the first v0.1.0 image even though GHCR had already pushed every tag.	2026-10-22 13:57:30 +01:00
tben	d0798a93a5	Add the self-hosted installer and release workflows	2026-10-20 07:02:58 +01:00