[SHIRO-838] promote source release with SHA-512 #152
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
|
one aspect I don't know how to code: but older releases are expected to be removed from distribution area, and instead downloaded from archive: https://archive.apache.org/dist/shiro/ |
bmarwell
approved these changes
Mar 5, 2022
Thanks, will do in another PR :) |
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.
different approach to apache/shiro#349
what is important is source release archive with its SHA-512 checksum, published in Apache distribution area https://dlcdn.apache.org/shiro/
convenience binaries published to Maven Central are just convenience pre-built binaries