publish.yml: on v* tags, check tag == v<brand_version!> and on main, build the amd64+arm64 image in one buildx run, push : and :latest, link the package, create the release. weekly-release.yml: port of the GitHub weekly cut; dry-run only until RELEASE_LIVE=1 and RELEASE_TOKEN exist.
publish.yml: on v* tags, check tag == v<brand_version!> and on main, build the amd64+arm64 image in one buildx run, push :<version> and :latest, link the package, create the release. weekly-release.yml: port of the GitHub weekly cut; dry-run only until RELEASE_LIVE=1 and RELEASE_TOKEN exist.
publish.yml replaces .github/workflows/publish.yml: on a v* tag it checks the
tag equals v<brand_version!> and is on main, builds the linux/amd64+arm64
image in one buildx run (the Dockerfile already cross-compiles, so only its
final stage goes through QEMU), pushes :<version> and :latest to the
registry, links the package, and creates the tag's release if it has none.
weekly-release.yml ports .github/workflows/release.yml: bump brand_version!
through the contents API, then create the release and so the tag, which
starts publish.yml. It only dry-runs until RELEASE_LIVE=1 and a
RELEASE_TOKEN secret exist.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
publish.yml: on v* tags, check tag == v<brand_version!> and on main, build the amd64+arm64 image in one buildx run, push : and :latest, link the package, create the release. weekly-release.yml: port of the GitHub weekly cut; dry-run only until RELEASE_LIVE=1 and RELEASE_TOKEN exist.