7 Commits

Include renames

Author	SHA1	Message	Date
Renovate Bot	0c38161989	fix(deps): update docker/setup-qemu-action action to v4	2026-06-12 11:11:04 +00:00
Renovate Bot	56ec85c17e	fix(deps): pin dependencies	2026-06-12 10:58:16 +00:00
Emma ThorpeandClaude Opus 4.8	d1803f06dd	fix: build multi-arch images for amd64 and arm64 ... Add QEMU setup and build for linux/amd64 and linux/arm64 (armv8), publishing a single multi-arch manifest. The nginx-unprivileged base image provides both architectures. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-11 17:20:20 +01:00
Emma ThorpeandClaude Opus 4.8	99084cc597	feat: auto-release images from conventional commits on main ... On each push to main, derive the next semantic version from the conventional-commit messages since the last v* tag (feat -> minor, fix/perf -> patch, \! or BREAKING CHANGE -> major) and, when a release is warranted, build and publish the image tagged X.Y.Z, X.Y, X and latest, then record an annotated vX.Y.Z tag for the next computation. Non-release pushes publish a sha-<short> image only. Configure Renovate to commit updates as fix(deps): so each merged Renovate PR registers as a patch change and is released and tagged automatically. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-11 17:04:40 +01:00
Emma ThorpeandClaude Opus 4.8	d296d88c4c	ci: tag images by semver and point latest at newest release ... Replace the raw latest-on-default-branch tag, which moved latest on every main push, with metadata-action's latest=auto flavor so latest follows the newest non-prerelease v* release. Add a {{major}} tag alongside the existing version and major.minor semver tags; branch and SHA tags remain for traceability of non-release builds. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-11 16:43:33 +01:00
Emma ThorpeandClaude Opus 4.8	7549aa6c90	fix: authenticate to container registry with a package-scoped PAT ... The auto-provided GITEA_TOKEN does not carry container registry write permission on most Gitea instances, causing docker login to fail with "unauthorized". Use a Personal Access Token supplied via the PACKAGES_TOKEN secret, with the package namespace owner as the username. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-11 16:31:32 +01:00
Emma ThorpeandClaude Opus 4.8	b28ec41ccb	ci: build and publish the container via Gitea Actions ... Build the image on pushes to main, version tags and pull requests, and push to the Gitea container registry (except on PRs) using the auto-provided GITEA_TOKEN. Tags are derived with docker/metadata-action. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-11 16:18:04 +01:00