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.14.1 -> 2.14.2 #479

Merged
merged 1 commit into from
Jan 30, 2023

Conversation

Picnic-Bot
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
com.fasterxml.jackson:jackson-bom import patch 2.14.1 -> 2.14.2

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

@Picnic-Bot
Copy link
Contributor Author

Picnic-Bot commented Jan 30, 2023

Suggested commit message:

Upgrade Jackson 2.14.1 -> 2.14.2 (#479)

See:
- https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.14.2
- https://github.com/FasterXML/jackson-bom/compare/jackson-bom-2.14.1...jackson-bom-2.14.2

@Stephan202 Stephan202 added this to the 0.9.0 milestone Jan 30, 2023
Copy link
Member

@Stephan202 Stephan202 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated the suggested commit message.

@rickie rickie force-pushed the renovate/com.fasterxml.jackson-jackson-bom-2.x branch from 7e2be87 to de1f248 Compare January 30, 2023 08:25
@github-actions
Copy link

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 changed the title Upgrade com.fasterxml.jackson:jackson-bom 2.14.1 -> 2.14.2 Upgrade Jackson 2.14.1 -> 2.14.2 Jan 30, 2023
@rickie rickie merged commit 4798f7c into master Jan 30, 2023
@rickie rickie deleted the renovate/com.fasterxml.jackson-jackson-bom-2.x branch January 30, 2023 08:36
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