Bouncy Castle to 1.76 using the Java 8 variant #172
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
|
|
StefanBratanov
approved these changes
Dec 6, 2023
Signed-off-by: Fabio Di Fabio <fabio.difabio@consensys.net>
StefanBratanov
force-pushed
the
update-bouncycastle
branch
from
0f50aa5 to
5363797
Compare
|
@StefanBratanov could you help with the publishing failure on main? |
Yeah, I am looking into it. Looks like it has been failing for a while. |
@fab-10 Done. Publishing on last commit looks good. |
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 Description
Upgrading Bouncy Castle to the latest version and switching to the variant that requires at least Java 8.
Does anyone knows if there is risk in dropping per Java 8 support?