Release automation: tag → build → push → Forgejo release with changelog #4

New issue

Open

opened 2026-07-07 16:51:21 +00:00 by claude-bot · 0 comments

claude-bot commented

2026-07-07 16:51:21 +00:00

Contributor

Goal

Cutting a release should be a single manual git tag; everything downstream is automated.

Scope

.forgejo/workflows/release.yml triggered on v* tags.
On tag:
- Build multi-arch images and push to the Forgejo registry (:<version> and :latest).
- Create a Forgejo release for the tag with generated/attached release notes.
- Source notes from CHANGELOG.md for the matching version section.
Keep the human step to just git tag vX.Y.Z && git push --tags.

Acceptance criteria

Pushing a vX.Y.Z tag builds and publishes images automatically
A Forgejo release object is created for the tag
Release body reflects the CHANGELOG entry for that version

Depends on: registry push, CHANGELOG.md.

## Goal Cutting a release should be a single manual `git tag`; everything downstream is automated. ## Scope - `.forgejo/workflows/release.yml` triggered on `v*` tags. - On tag: - Build multi-arch images and push to the Forgejo registry (`:<version>` and `:latest`). - Create a Forgejo release for the tag with generated/attached release notes. - Source notes from `CHANGELOG.md` for the matching version section. - Keep the human step to just `git tag vX.Y.Z && git push --tags`. ## Acceptance criteria - [ ] Pushing a `vX.Y.Z` tag builds and publishes images automatically - [ ] A Forgejo release object is created for the tag - [ ] Release body reflects the CHANGELOG entry for that version Depends on: registry push, CHANGELOG.md.

claude-bot added the

labels

2026-07-07 16:53:25 +00:00

claude-bot referenced this issue

2026-07-07 16:59:04 +00:00

Move CI/CD to Forgejo Actions; add CHANGELOG; issues-driven roadmap #19