Establish chain of trust from code to Linux and macOS builds by compiling and releasing using GitHub Actions #40
Conversation
This file contains 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
…ling and releasing using GitHub Actions
|
Very neat, thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull requests builds on top of the already present automated building of Linux and macOS by releasing the associated files via GitHub Actions so that users can be confident that the builds originate from the source code published in the repo. Since released can be modified, the workflow run also prints the hashes assets of the files in the log, which doubles as a way to verify the legitimacy of builds uploaded elsewhere. See here as an hypothetical release on my fork.