Add tag-based release workflow #45

Merged

miro merged 9 commits from claude/release-strategy-36db27 into main 2026-10-10 19:39:20 +00:00

Conversation 0 Commits 9 Files changed 13 +331 -21

miro commented 2026-10-10 19:22:03 +00:00

Owner

Copy link

Summary

• Merges to main no longer deploy. CI publishes sha-<short> images only (no more :latest) and ignores changes that only touch docker-compose.prod.yml.
• New release.yml, run with fj actions dispatch release.yml main: retags the already-built image as CalVer YYYY.M.N, pins it in docker-compose.prod.yml, commits and tags v<version>, creates a Forgejo release with git-cliff notes, then calls the deploy webhook (gitsync rereads the compose file).
• Adds cliff.toml and a Releases section in the README.

Before merging

• Add the RELEASE_TOKEN secret (PAT with repo write scope).
• Dispatch the first release right after merge: prod compose still says :latest, which CI no longer updates. The first release's notes cover the whole history.
• Set up a container cleanup rule for ^sha- versions (keep release tags matching ^\d{4}\.\d+\.\d+$).

Not tested

The workflows haven't been run. Likely trouble spots: node on the docker runner (used to build the release JSON) and $GITHUB_SERVER_URL resolving to the right host. A failure before the push step deploys nothing.

## Summary - Merges to `main` no longer deploy. CI publishes `sha-<short>` images only (no more `:latest`) and ignores changes that only touch `docker-compose.prod.yml`. - New `release.yml`, run with `fj actions dispatch release.yml main`: retags the already-built image as CalVer `YYYY.M.N`, pins it in `docker-compose.prod.yml`, commits and tags `v<version>`, creates a Forgejo release with `git-cliff` notes, then calls the deploy webhook (gitsync rereads the compose file). - Adds `cliff.toml` and a Releases section in the README. ## Before merging - Add the `RELEASE_TOKEN` secret (PAT with repo write scope). - Dispatch the first release right after merge: prod compose still says `:latest`, which CI no longer updates. The first release's notes cover the whole history. - Set up a container cleanup rule for `^sha-` versions (keep release tags matching `^\d{4}\.\d+\.\d+$`). ## Not tested The workflows haven't been run. Likely trouble spots: `node` on the `docker` runner (used to build the release JSON) and `$GITHUB_SERVER_URL` resolving to the right host. A failure before the push step deploys nothing.

miro added 1 commit 2026-10-10 19:22:04 +00:00

Add tag-based release workflow ... 9fef9de61a

Merges to main now only publish sha-<short> images. A manually dispatched
release workflow retags the image as CalVer, pins it in docker-compose.prod.yml,
tags, creates a release with git-cliff notes and triggers the deploy.

miro added 1 commit 2026-10-10 19:25:37 +00:00

Show the release version in the nav; move release creation into a script ... f8acba82f7

APP_VERSION is set at runtime from docker-compose.prod.yml (the image is
retagged, not rebuilt, so the version can't be baked in at build time).

miro added 1 commit 2026-10-10 19:28:17 +00:00

Ship the version as a thin image layer instead of an env var ... 9749baaa40

The release workflow builds a per-arch layer adding /app/VERSION on top of the
image CI built, then publishes the multi-arch tag from those.

miro added 1 commit 2026-10-10 19:28:52 +00:00

Link the nav version to its release page 65c01c1741

miro force-pushed claude/release-strategy-36db27 from 65c01c1741 to 156a2df092 2026-10-10 19:33:27 +00:00 Compare

miro added 1 commit 2026-10-10 19:33:46 +00:00

Refetch the version every 10 minutes instead of never 64e37374ca

miro added 1 commit 2026-10-10 19:34:47 +00:00

Use FORGEJO_* variables in the release and image-tag steps 4ba146d5fb

miro added 1 commit 2026-10-10 19:35:54 +00:00

Drop a comment 2d28c4f3be

miro added 1 commit 2026-10-10 19:37:52 +00:00

Keep the first release's notes short a8fd3b1ae8

miro merged commit 508b528918 into main 2026-10-10 19:39:20 +00:00

miro deleted branch claude/release-strategy-36db27 2026-10-10 19:39:20 +00:00

miro referenced this pull request from a commit 2026-10-10 19:39:21 +00:00

Add tag-based release workflow (#45)

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

miro/files!45

No description provided.