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-core from 2.18.0 to 2.18.1 #556

Merged
merged 1 commit into from
Dec 10, 2024

Conversation

pkiraly
Copy link
Owner

@pkiraly pkiraly commented Dec 1, 2024

snyk-top-banner

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

ℹ️ 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 1 version 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:

….18.1

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

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

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

sonarqubecloud bot commented Dec 1, 2024

@pkiraly pkiraly merged commit c64ff6b into main Dec 10, 2024
8 checks passed
@pkiraly pkiraly deleted the snyk-upgrade-9f336a5b7b9a682ef858bff2f48281b6 branch December 19, 2024 21:01
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