Skip to content

Bump org.apache.logging.log4j:log4j-bom from 2.25.4 to 2.26.0 #395

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.

Sign up for GitHub

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

Merged
docwho2 merged 1 commit into from
May 7, 2026
Merged

Bump org.apache.logging.log4j:log4j-bom from 2.25.4 to 2.26.0 #395

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-bom</artifactId>
<version>2.25.4</version>
<version>2.26.0</version>
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot May 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Revert to a published Log4j BOM

This version is not available in Maven Central yet: the Log4j BOM index I checked on May 7, 2026 lists 2.25.4 as the latest published 2.x BOM and has no 2.26.0 entry. Because this is an imported BOM in the parent POM, any Maven build that resolves from Central will fail during project model construction with a non-resolvable import POM before compiling any module.

Useful? React with 👍 / 👎.

<type>pom</type>
<scope>import</scope>
</dependency>
Expand Down
Loading