Repository navigation
Bump vulnerable versions in IT fixtures where the version is incidental - #1723
Merged
Merged
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
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.
Clears Dependabot alerts on four IT fixtures: maven-core 3.0/3.6.3 → 3.9.16 in
analyze-ignore-used-undeclared-dependency,treeandtree-scope(golden trees regenerated), and logback-core 1.5.6 → 1.5.34 inmdep-689-apply-filtering-go-offline-goal.The PR does not touch fixtures where the old version is what the test exercises:
list-repositoriesasserts on a repository declared in maven-core 3.2.5's POM chain,copy-dependencies-with-conflictneedsorg.jdom:jdomandorg.lucee:jdomat the same version, andtree-verbosehas its golden tree built around batik-bridge 1.7.Verified:
mvn -P run-its verifyon these four ITs → passed under Maven 3.9.16, 4.0.0-rc-6 and 4.0.0-rc-7.