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

Upgrade Jackson 2.18.2 -> 2.18.3 #1575

Merged
merged 1 commit into from
Mar 9, 2025
Merged

Upgrade Jackson 2.18.2 -> 2.18.3 #1575

merged 1 commit into from
Mar 9, 2025

Conversation

Picnic-DevPla-Bot
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
Jackson import patch 2.18.2 -> 2.18.3

  • If you want to rebase/retry this PR, check this box

@Picnic-DevPla-Bot
Copy link
Contributor Author

Picnic-DevPla-Bot commented Mar 2, 2025

Suggested commit message:

Upgrade Jackson 2.18.2 -> 2.18.3 (#1575)

See:
- https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.18.3
- https://github.com/FasterXML/jackson-bom/compare/jackson-bom-2.18.2...jackson-bom-2.18.3

Copy link

github-actions bot commented Mar 2, 2025

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

@rickie rickie modified the milestones: 0.22.0, 0.21.0 Mar 3, 2025
@Stephan202 Stephan202 force-pushed the renovate/jackson-2.x branch from 80c4514 to a1383b3 Compare March 9, 2025 10:33
Copy link

github-actions bot commented Mar 9, 2025

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

Copy link

sonarqubecloud bot commented Mar 9, 2025

@Stephan202 Stephan202 merged commit 9316d81 into master Mar 9, 2025
17 checks passed
@Stephan202 Stephan202 deleted the renovate/jackson-2.x branch March 9, 2025 10:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants