Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Override Spring BOM for SnakeYAML to force version 2.2 #13255

Merged
merged 2 commits into from
Dec 5, 2023

Conversation

guillermocalvo
Copy link
Contributor

to override SpringBoot BOM

to override SpringBoot BOM
@puneetbehl puneetbehl changed the title Add SnakeYAML BOM Override Spring BOM for SnakeYAML to force version 2.2 Dec 5, 2023
@puneetbehl puneetbehl merged commit 1373750 into 4.1.x Dec 5, 2023
3 checks passed
@puneetbehl puneetbehl deleted the snakeyamlbom-grails4 branch December 5, 2023 08:13
guillermocalvo added a commit that referenced this pull request Jan 8, 2024
Revert "Override Spring BOM for SnakeYAML to force version 2.2  (#13255)"
- This reverts commit 1373750.

Revert "Upgrade snakeyaml; replace deprecated constructor calls"
- This reverts commit 64a2806.
guillermocalvo added a commit that referenced this pull request Jan 8, 2024
Revert "Override Spring BOM for SnakeYAML to force version 2.2  (#13255)"
- This reverts commit 1373750.

Revert "Upgrade to SnakeYaml 2.2 and use SafeContructor to prevent accessing the classpath (#13207)"
- This reverts commit dd02741.
- This reverts commit 980d835.
- This reverts commit 64a2806.
puneetbehl pushed a commit that referenced this pull request Jan 8, 2024
Revert "Override Spring BOM for SnakeYAML to force version 2.2  (#13255)"
- This reverts commit 1373750.

Revert "Upgrade to SnakeYaml 2.2 and use SafeContructor to prevent accessing the classpath (#13207)"
- This reverts commit dd02741.
- This reverts commit 980d835.
- This reverts commit 64a2806.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants