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

[Snyk] Upgrade com.fasterxml.jackson.core:jackson-annotations from 2.17.2 to 2.18.0 #531

Merged
merged 1 commit into from
Oct 30, 2024

Conversation

pkiraly
Copy link
Owner

@pkiraly pkiraly commented Oct 27, 2024

snyk-top-banner

Snyk has created this PR to upgrade com.fasterxml.jackson.core:jackson-annotations from 2.17.2 to 2.18.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 2 versions ahead of your current version.

  • The recommended version was released on a month ago.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

….2 to 2.18.0

Snyk has created this PR to upgrade com.fasterxml.jackson.core:jackson-annotations from 2.17.2 to 2.18.0.

See this package in maven:
com.fasterxml.jackson.core:jackson-annotations

See this project in Snyk:
https://app.snyk.io/org/pkiraly/project/0714a1c8-258c-4035-b3ee-1ea3a702652a?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

@pkiraly pkiraly merged commit 44d667a into main Oct 30, 2024
8 checks passed
@pkiraly pkiraly deleted the snyk-upgrade-862b4d67581f75ee1b799aa70a50277f branch November 4, 2024 13:53
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.

2 participants