🚸 feat: Change default checksumMode from local to remote #1199
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
LogFlames
changed the title
|
Promising PR, thanks @LogFlames
Merged together? Can we rather serialize? |
Yes thats a better idea, but we should fix #1193 first. |
Enable sha256 and sha512 for maven central In case sha256/sha512 is missing from remote, download file, verify with sha1, and calculate new checksum
LogFlames
force-pushed
the
1192-checksums-change-default-to-remote
branch
from
12243a0 to
63d8377
Compare
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.
See #1192.
This change should be merged together with #1193 to ensure our default is always to use strong checksums. Also note that when regenerating old lockfiles the config will be loaded from those files as discussed in #1188. A manual update would have to be created using: