Release by itself at every merge #38

Merged
squid merged 2 commits from ci/semantic-release into main 2026-11-16 12:09:16 +00:00
Owner

Closes #37

At every merge into main a workflow (.forgejo/workflows/release.yml) makes a release by itself.

  • semantic-release reads the Conventional Commits since the last release (fix and perf: patch, feat: minor, feat! or BREAKING CHANGE: major; docs, test, chore, ci and style make none), writes CHANGELOG.md, tags the commit and makes the release on the forge. The commit with the changelog says [skip ci].
  • With a release, the image is built from the tag and pushed to git.kmalloc.org/squid/sonda as X.Y.Z, X.Y and latest. The runner has no Docker, so it is built with kaniko.
  • The version is no longer in the code: the release sets it (-X main.version, in the Dockerfile and the Makefile). GET /version and the User-Agent of the providers say it; a build that no release made says dev.
  • The secret FORGEJO_TOKEN is set in the repository (a token with write:repository and write:package, kept in Bitwarden).
  • README: a Releases section with the table of commit prefixes.
Closes #37 At every merge into main a workflow (`.forgejo/workflows/release.yml`) makes a release by itself. - semantic-release reads the Conventional Commits since the last release (fix and perf: patch, feat: minor, feat! or BREAKING CHANGE: major; docs, test, chore, ci and style make none), writes `CHANGELOG.md`, tags the commit and makes the release on the forge. The commit with the changelog says `[skip ci]`. - With a release, the image is built from the tag and pushed to `git.kmalloc.org/squid/sonda` as `X.Y.Z`, `X.Y` and `latest`. The runner has no Docker, so it is built with kaniko. - The version is no longer in the code: the release sets it (`-X main.version`, in the Dockerfile and the Makefile). `GET /version` and the User-Agent of the providers say it; a build that no release made says `dev`. - The secret `FORGEJO_TOKEN` is set in the repository (a token with write:repository and write:package, kept in Bitwarden). - README: a Releases section with the table of commit prefixes.
At every merge into main a workflow reads the Conventional Commits since the last release,
works out the version, writes CHANGELOG.md, tags the commit and makes the release on the
forge; when there is a release it builds the image from the tag and pushes it to
git.kmalloc.org/squid/sonda as X.Y.Z, X.Y and latest. The runner has no Docker, so the
image is built with kaniko.

The version is no longer written in the code: the release sets it (-X main.version) in the
Dockerfile and the Makefile, and a build that no release made says dev.
The preset of the commit messages in its 10th version cannot be read by the generator of
the release notes that semantic-release 25 comes with: use its 8th, and pin the
analyzer and the generator too. Found by a dry run before the first release.
squid merged commit 3490849837 into main 2026-11-16 12:09:16 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
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
squid/sonda!38
No description provided.