Repository navigation
ci: release workflow for static Linux + macOS binaries - #4
Merged
Merged
Conversation
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
1 participant
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.
On a
v*tag matching Cargo.toml, three jobs build and test:linux-amd64andlinux-arm64: musl, static, asserted withfile.darwin-arm64.Each job also checks the binary:
--versionruns.checkpasses on the example config with everyREPLACE_MEfilled by a freshgen-secretverifier.The binary is packaged with README, LICENSE, the example config, the southbound contract and the reference daemon. A single publish job then creates the release, with all three tarballs and
SHA256SUMS.README: download instructions.
Tested: the verifier-substitution step on macmini (3 placeholders replaced,
checkOK). The workflow itself is verified by the v0.1.0 tag after merge.