Repository navigation
Dependabot support for spring security versions - #817
Merged
Merged
Conversation
timea-solid
approved these changes
Dec 1, 2023
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
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.
Similar to how multiple RDF4J versions need to be managed for different parts of the JCL, spring support depends on the Java runtime (Spring 5 works on Java11, Spring 6 requires Java 17+). This restructures the dependabot version management a bit so that the project can better support these differences.
In this case, the
java-11profile is inverted, and changed to ajava-17profile. The Java 11-based Spring version is defined in the root pom.xml while the Java 17+ version is defined in the spring/pom.xml file.