Releasing
Releases are cut from main by pushing a version tag.
-
Make sure CI is green on
mainandCHANGELOG.mdhas an entry for the version: move the Unreleased items under a new## [X.Y.Z] - YYYY-MM-DDheading and add the comparison link at the bottom. -
Bump
versioninCargo.tomland runcargo buildsoCargo.lockfollows. Commit both with the changelog. -
Tag and push:
git tag -a vX.Y.Z -m "bot-cooker X.Y.Z" git push origin vX.Y.Z
The Release workflow then:
- builds static binaries for Linux x86-64 and ARM64 (musl) and Windows
x86-64, with
README.md,LICENSE,NOTICEand the sample configuration, and attaches them with aSHA256SUMSfile to a GitHub release; - builds the container image natively on x86-64 and ARM64 runners and
publishes
ghcr.io/koval01/bot-cooker:X.Y.Zand:latest.
After the first release, set the package’s visibility to public in the repository’s Packages settings; the one-line installer pulls the image without logging in.
If a release changes what existing keys’ personas look like, say so at the top of its changelog entry.