This repository was archived by the owner on Dec 16, 2021. It is now read-only.
Update version to 2.3 & pull sha256sum instead of hardcoding it #10
+7
−3
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
* Also allow the VERSION & EXT to pull from releases to be build argument configuration, but correct by default.
|
Personally, I want to get rid of that sha256 checksum verification entirely. It's a waste of time that doesn't add any security. I'll cherry pick the version update from this PR, though. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Set the VERSION & EXT to pull from releases to be build argument configuration. This should allow quicker turn around time to bump the VERSION without needing to also manually grab the sha256 to hardcod into the Dockerfile.