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

fix(deps): update log4j2 monorepo to v2.23.1 #2896

Merged
merged 1 commit into from
Mar 10, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 10, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
org.apache.logging.log4j:log4j-slf4j2-impl (source) 2.23.0 -> 2.23.1 age adoption passing confidence
org.apache.logging.log4j:log4j-core (source) 2.23.0 -> 2.23.1 age adoption passing confidence

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


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

This PR has been generated by Mend Renovate. View repository job log here.

@hazendaz hazendaz self-assigned this Mar 10, 2024
@hazendaz hazendaz merged commit 5b3469c into master Mar 10, 2024
31 checks passed
@renovate renovate bot deleted the renovate/log4j2-monorepo branch March 10, 2024 20:52
Copy link

sonarcloud bot commented Mar 10, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

@hazendaz hazendaz added this to the SpotBugs 4.8.4 milestone Mar 14, 2024
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.

None yet

1 participant