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

Bump org.apache.logging.log4j:log4j-bom from 2.23.0 to 2.24.2 in /data-prepper-expression #5232

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 1, 2024

Bumps org.apache.logging.log4j:log4j-bom from 2.23.0 to 2.24.2.

Release notes

Sourced from org.apache.logging.log4j:log4j-bom's releases.

2.24.2

Release Notes

This release fixes a critical bug in Log4j API initialization code, which can cause LogManager.getLogger() to return null under certain conditions. See #3143 for details.

Fixed

  • Fix key removal issues in Thread Context (#3048)
  • Use hard references to Loggers in LoggerRegistry. (#3143)
  • Fix ArrayIndexOutOfBoundsException in JSON Template Layout truncated exception resolver (#3216)

2.24.1

This release contains mainly bug fixes of problems encountered with the thread context map, logger registry and configuration reloading.

It also enhances integration tests to use Docker images of the most recent releases of MongoDB and Elastic Search.

Changed

  • Rework LoggerRegistry to make it MessageFactory-namespaced. This effectively allows loggers of same name, but different message factory. (#2936)
  • Enable Docker-based tests in CI for JSON Template Layout (#2953)

Fixed

  • Switch MongoDB tests to use Docker. (#2229)
  • Fix reloading of the configuration from an HTTP(S) source (#2937)
  • Fix putAll() in the default thread context map implementation (#2942)

Updated

  • Update org.apache.logging:logging-parent to version 11.3.0

2.24.0

The 2.24.0 version of Log4j API has been enhanced with changes from the 3.x branch and will be used by both Log4j 2 Core and Log4j 3 Core releases. The changes include:

  • A faster default ThreadContextMap.
  • Enhanced GraalVM support: native binaries that use Log4j API will no longer require additional GraalVM configuration.
  • The configuration properties subsystem now only accepts the official pre-2.10 property names and the normalized post-2.10 names. Check your configuration for typos.

Documentation

The Apache Log4j 2 website has been almost entirely rewritten to provide improved documentation and faster access to the information you need.

Bridges

The JUL-to-Log4j API and Log4j 1-to-Log4j API bridges will no longer be able to modify the configuration of Log4j Core by default. If such a functionality is required, it must be explicitly enabled.

Modules

... (truncated)

Commits
  • e65538d Update the project.build.outputTimestamp property
  • ae1137b Prepare release notes for version 2.24.2
  • efba2fb Fix off-by-one in StackTraceStringResolver (#3216)
  • 81e1f06 Fix key removal issues in Thread Context (#3210)
  • a1dfa85 Removes weak references from LoggerRepository (2.24.x branch) (#3209)
  • 3fc2088 Bump version to 2.24.2-SNAPSHOT
  • 8ee9387 Update the project.build.outputTimestamp property
  • 767be86 Prepare release notes version 2.24.1
  • a92713c Pin Cassandra transitive deps
  • a05d921 Revert "Prepare release notes for 2.24.1"
  • Additional commits viewable in compare view

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [org.apache.logging.log4j:log4j-bom](https://github.com/apache/logging-log4j2) from 2.23.0 to 2.24.2.
- [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.23.0...rel/2.24.2)

---
updated-dependencies:
- dependency-name: org.apache.logging.log4j:log4j-bom
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file java Pull requests that update Java code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants