chore: bump org.apache.logging.log4j:log4j-api from 2.26.0 to 2.26.1 - #2610
Conversation
Bumps org.apache.logging.log4j:log4j-api from 2.26.0 to 2.26.1. --- updated-dependencies: - dependency-name: org.apache.logging.log4j:log4j-api dependency-version: 2.26.1 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
|
phipag
left a comment
There was a problem hiding this comment.
Reviewed and approved by @phipag. Bumps the shared log4j.version property to 2.26.1 across the root pom and three example poms, so this PR is a superset of #2611 and #2609. Log4j 2.26.1 is a patch release with no CVEs, no dependency updates, and no API removals or deprecations. Because every log4j artifact is driven off the single version property, log4j-api cannot drift from log4j-core. All six pinned artifacts are confirmed published on Maven Central. All CI checks pass across Java 11, 17, 21, and 25.
|
Tick the box to add this pull request to the merge queue (same as
|



Bumps org.apache.logging.log4j:log4j-api from 2.26.0 to 2.26.1.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.