Add release workflow for tag-based publishing#4
Merged
amackillop merged 1 commit intomasterfrom Mar 30, 2026
Merged
Conversation
Triggered on v* tags. Verifies the tag matches the Cargo.toml version, builds static binaries for x86_64 and aarch64 via Nix, creates a GitHub Release with both binaries attached, then builds and pushes multi-arch container images to GHCR. The container pipeline builds arch-specific images on native runners (avoiding slow QEMU emulation), pushes per-arch tags, then assembles a multi-arch manifest. The "latest" tag only moves forward when the pushed tag is the highest semver, so publishing a patch for an older release line won't clobber it. All third-party actions are pinned to full commit SHAs.
martinsaposnic
approved these changes
Mar 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Triggered on v* tags. Verifies the tag matches the Cargo.toml version, builds static binaries for x86_64 and aarch64 via Nix, creates a GitHub Release with both binaries attached, then builds and pushes multi-arch container images to GHCR.
The container pipeline builds arch-specific images on native runners (avoiding slow QEMU emulation), pushes per-arch tags, then assembles a multi-arch manifest. The "latest" tag only moves forward when the pushed tag is the highest semver, so publishing a patch for an older release line won't clobber it.
All third-party actions are pinned to full commit SHAs.