Repository navigation
馃敀 fix(deps): pin patched Jackson 3.x BOM for test framework - #263
Merged
gaborbernat merged 1 commit intoOct 7, 2026
Merged
Conversation
The platform test framework's resolution rule pinned the Jackson 3.x BOM to 3.1.6, which four open Dependabot alerts (tox-dev#55-tox-dev#58) cover for jackson-core and jackson-databind. 3.1.7 is the first patched release.
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.
Four Dependabot alerts (#55-#58) cover
tools.jackson.core:jackson-coreandtools.jackson.core:jackson-databind3.0.0 through 3.1.6: a quadratic forward-reference completion, unbounded raw-type-ID retention, a ReDoS in number parsing, and unbounded StringBuilder growth from an unlimited error-token length. The platform test framework pulls these in throughtools.jackson:jackson-bom, and the resolution rule added for that BOM already pinned it to 3.1.6, the last vulnerable release, rather than the first patched one.3.1.7 is that patched release. The rule now pins the BOM there, which brings
jackson-coreandjackson-databindwith it since both are BOM-managed constraints.