auto-pipeline
auto-pipeline copied to clipboard
chore(deps): bump org.apache.logging.log4j:log4j-bom from 2.23.1 to 2.24.1 in /auto-pipeline-examples
Bumps org.apache.logging.log4j:log4j-bom from 2.23.1 to 2.24.1.
Release notes
Sourced from org.apache.logging.log4j:log4j-bom's releases.
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
LoggerRegistryto make itMessageFactory-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-parentto version11.3.02.24.0
The
2.24.0version of Log4j API has been enhanced with changes from the3.xbranch 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
The following Log4j Core additional modules have been removed:
log4j-flume-ngThe module is no longer part of the release process and will follow its own release lifecycle. Please manage your dependencies usinglog4j-bomto always use its latest version.
log4j-kubernetesThe module has been moved to the Fabric8.io Kubernetes project and follows the Fabric8.io release lifecycle.
log4j-mongodb3
... (truncated)
Commits
8ee9387Update theproject.build.outputTimestampproperty767be86Prepare release notes version2.24.1a92713cPin Cassandra transitive depsa05d921Revert "Prepare release notes for2.24.1"755497dRevert "Single constructor forConfigurationSource"a01f7e4Prepare release notes for2.24.15d6bd3cClean up changelog entries9c798aeUpdatecom.github.luben:zstd-jnito version1.5.6-6(#2998)a3d138bUpdatecommons-io:commons-ioto version2.17.0(#2984)13b5fdaUpdateorg.slf4j:slf4j-nopto version2.0.16(#2955)- Additional commits viewable in compare view
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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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)