build(deps): bump org.apache.logging.log4j:log4j-bom from 2.25.3 to 2.25.4#252
Merged
david-waltermire merged 1 commit intodevelopfrom Apr 23, 2026
Conversation
2 tasks
david-waltermire
previously approved these changes
Apr 23, 2026
Contributor
david-waltermire
left a comment
There was a problem hiding this comment.
Dependency bump: org.apache.logging.log4j:log4j-bom 2.25.3 → 2.25.4. Previous Trivy CI failure was infrastructure (install.sh) — fixed on develop via #256. Rebased.
Contributor
|
@dependabot rebase |
Contributor
Author
|
Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry! If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request |
Contributor
|
@dependabot recreate |
Bumps [org.apache.logging.log4j:log4j-bom](https://github.com/apache/logging-log4j2) from 2.25.3 to 2.25.4. - [Release notes](https://github.com/apache/logging-log4j2/releases) - [Changelog](https://github.com/apache/logging-log4j2/blob/2.x/RELEASE-NOTES.adoc) - [Commits](apache/logging-log4j2@rel/2.25.3...rel/2.25.4) --- updated-dependencies: - dependency-name: org.apache.logging.log4j:log4j-bom dependency-version: 2.25.4 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
11d2116 to
692f761
Compare
david-waltermire
approved these changes
Apr 23, 2026
Contributor
david-waltermire
left a comment
There was a problem hiding this comment.
Dependency bump: org.apache.logging.log4j:log4j-bom 2.25.3 → 2.25.4. Re-approval after dependabot recreate to resolve conflict.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps org.apache.logging.log4j:log4j-bom from 2.25.3 to 2.25.4.
Release notes
Sourced from org.apache.logging.log4j:log4j-bom's releases.
Commits
0628e53Update theproject.build.outputTimestamppropertya2590b4Add debug logs for successful resource loading inLoader(#4060)b788154Changelog for additional fixes59bd6b3Avoid referring toPluginBuilderAttribute.classinPluginProcessor(#4041)79568dbTakeThrowable#toString()into account while rendering stack traces in Patt...0881bc5Add versioning and support policy information (#3341)0543b52docs: recommend use of appropriately scoped trust roots (#4006)7a1e0adFix warning when last argument is null (#4014)5286148Remove Log4j Jakarta EE link from navigation file (#4025)adcda32Retire Log4j Scala (#4030)