Build checksums #232
Merged
Build checksums #232
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
…so testing in a branch.
Windows: only do the 2 files we distribute, since they are also signed. MacOS requires post-signing so we want to checksum all. But it's super slow. Use MD5 instead and filter the giant pointless botocore data directory.
…d move the tar process into github action
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.
Add checksums to build process, so anyone can verify the builds.
MacOS gets signed after this build, so not sure what files will have their checksum changed (or if it's only added files). To play is safe, checksum whole .app file at a time.