Commit graph sonda/.forgejo/workflows
Author SHA1 Message Date
tgiachi
b37e3db037 feat: publish the Docker image for ARM as well
The image is now made for amd64 and for arm64, and each tag (X.Y.Z, X.Y,
latest) points at both, so a Raspberry Pi or an ARM NAS pulls the right one.

- Dockerfile: the web and Go stages run on the builder and the Go program is
  cross-compiled (GOARCH from SONDA_ARCH or TARGETARCH); what the image needs
  besides the program (time zones, the user, the folders) is made in a stage
  of the builder, so the last stage runs no command and needs no emulation.
- release workflow: the runner has no Docker and cannot run ARM, and kaniko
  takes the base of every stage for one platform, so the arm64 image starts
  from the arm64 Alpine by digest (found at each release), kaniko builds one
  image per architecture, and crane sets the architecture of each and joins
  them under the tags.
2026-11-16 14:33:41 +01:00
tgiachi
9905c4788f ci: pin the release tools to versions that work together
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.
2026-11-16 13:08:58 +01:00
tgiachi
a478c95536 ci: release by itself at every merge, with semantic-release
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.
2026-11-16 13:07:17 +01:00