scripts/deploy.sh: generate sha256sum of artifacts #9669
Merged
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
navarroaxel
approved these changes
Dec 25, 2022
navarroaxel
changed the title
kbdharun
approved these changes
Dec 26, 2022
Co-authored-by: Axel Navarro <[email protected]>
navarroaxel
approved these changes
Dec 26, 2022
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.
PR modifies the deploy process so that a
sha256sumsfile is generated that has the SHA256 hash of each asset file that was generated during the deploy. This can be used by folks to verify that theziporindex.jsonorpdfthat they downloaded matches the one we built, as well as could be used as an easy way to tell if the source has changed at all since the previous update (which would help me tackle tldr-pages/tldr-c-client#94).