[12811] Keep plexus-cipher at 2.0: POM note - #12879
Merged
Merged
Conversation
This was referenced Aug 28, 2026
slachiewicz
added
mvn3
dependencies
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Keep plexus-cipher at 2.0 on this branch, per the decision in #12811.
plexus-cipher 2.1.0 uses an incompatible key derivation function, so ciphertext encrypted with 2.0 no longer decrypts. That kind of break doesn't belong on a patch release.
This PR adds a short comment above the
<cipherVersion>property in the root POM asking maintainers and Dependabot not to bump it. The matching Dependabot ignore is in #12880.