Bump jakarta.xml.bind to allow 4.0.x #3289
Open
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
Collaborator
|
Checks Summary Last run: 2025-10-23T14:06:04.665Z Code Risk Analyzer vulnerability scan found 1 vulnerabilities:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Hey there,
This is a small PR to address an issue we encountered recently.
We're trying to update our internal dependencies to address some outdated ones, and would like to upgrade the Jakarta Bind-API to 4.0.*, which is just barely outside the supported range.
I validated that all tests are passing with this change, and do not expect any third-party degradations (but please let me know if I've missed something).I'd be happy to contribute further.
(this would also address #3265)
Thanks in advance