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 org.apache.logging.log4j:log4j-api from 2.24.0 to 2.24.1 #1991

Merged
merged 1 commit into from
Oct 17, 2024

Conversation

ihrasko
Copy link
Collaborator

@ihrasko ihrasko commented Oct 16, 2024

snyk-top-banner

Snyk has created this PR to upgrade org.apache.logging.log4j:log4j-api from 2.24.0 to 2.24.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 22 days 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:

Snyk has created this PR to upgrade org.apache.logging.log4j:log4j-api
from 2.24.0 to 2.24.1.

https://logging.apache.org/log4j/2.x/release-notes.html#release-notes-2-24-1

Signed-off-by: Ivan Hrasko <ivan.hrasko@pantheon.tech>
@ihrasko ihrasko force-pushed the snyk-upgrade-007e72f17c04f2822f81a8c5dac6590e branch from 64b428c to 282670c Compare October 17, 2024 10:45
Copy link

@ihrasko ihrasko merged commit 7bf0a2b into main Oct 17, 2024
10 of 11 checks passed
@ihrasko ihrasko deleted the snyk-upgrade-007e72f17c04f2822f81a8c5dac6590e branch October 17, 2024 11:19
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