AJ-1026: actually upgrade snakeyaml #229
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
|
Kudos, SonarCloud Quality Gate passed!
|
yuliadub
approved these changes
May 8, 2023
aaronkanzer
approved these changes
May 8, 2023
calypsomatic
approved these changes
May 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In #226 I tried to upgrade snakeyaml, but was ineffective. I specified a dependency constraint … but since the versions controlled by
io.spring.dependency-managementtake precedence, the constraint did nothing.This comment helps with confidence that Spring Boot 2.7.11 and snakeyaml 2.0 work ok together.
In this PR:
dependencyManagementblock, which is theio.spring.dependency-management-specific way to do it