john-okeefe
4fe5aa25f8
Release / build-and-push (push) Successful in 1m17s
Add .gitea/workflows/release.yml: on v* tag push (or manual dispatch) build the Docker image and push git.linuxhg.com/games-database/games-api:<tag> plus :latest, then create/update the Gitea Release from the annotated tag message. Main-branch pushes do nothing so WIP never ships. Add cliff.toml (conventional-commit grouping for release notes), Makefile release target (cliff notes into annotated tag, then push), and ./release wrapper (accepts 1.0 or v1.0). Release flow: ./release v1.0, matching bookhoard. Requires a REGISTRY_TOKEN repo Actions secret (PAT with write:package and write:repository); Gitea's auto token lacks package scope.
16 lines
469 B
Bash
Executable File
16 lines
469 B
Bash
Executable File
#!/usr/bin/env sh
|
|
# Project-attached wrapper around `make release` so you can run:
|
|
# ./release v0.1.0 (or) ./release 0.1.0
|
|
# instead of:
|
|
# make release VERSION=v0.1.0
|
|
# Lives in the repo (no machine-specific alias needed).
|
|
set -eu
|
|
|
|
[ "$#" -ge 1 ] || { echo "Usage: ./release v0.1.0" >&2; exit 1; }
|
|
|
|
# Accept "0.1.0" or "v0.1.0"; ensure the tag starts with 'v' (the workflow
|
|
# only triggers on v* tags).
|
|
VERSION="v${1#v}"
|
|
|
|
exec make release "VERSION=${VERSION}"
|