Adding my +1. With that, the release passes with 4 binding +1 votes from Jan, Piotr, Gary, and me. I will continue the release process.
On Mon, May 4, 2026 at 9:45 AM Volkan Yazıcı <[email protected]> wrote: > > This is a vote to release the Apache Log4j `2.26.0`. > > Website: https://logging.staged.apache.org/log4j/2.26.0 > GitHub: https://github.com/apache/logging-log4j2 > Commit: c1ad2a66cc90e643ec319b9e131764c9710bebc5 > Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j/2.26.0 > Nexus: > https://repository.apache.org:443/content/repositories/orgapachelogging-1325 > Signing key: 0x077e8893a6dcc33dd4a4d5b256e73ba9a0b592d0 > Review kit: > https://logging.apache.org/logging-parent/release-review-instructions.html > > Please download, test, and cast your votes on this mailing list. > > [ ] +1, release the artifacts > [ ] -1, don't release, because... > > This vote is open for 72 hours and will pass unless getting a > net negative vote count. All votes are welcome and we encourage > everyone to test the release, but only the Logging Services PMC > votes are officially counted. At least 3 +1 votes and more > positive than negative votes are required. > > == Release Notes > > This minor release delivers all the fixes in the `[2.25.0, 2.25.4]` > version range, plus some new fixes, and several other > improvements and features. > > === Added > > * Add a new `ConfigurationFactory::getConfiguration` method > accepting multiple `URI`s (#3775, #3921) > * Add and export > `org.apache.logging.log4j.core.pattern.NamedInstantPattern` > enabling users to programmatically access named date > & time patterns supported by Pattern Layout (#3789) > * Add `log4j.plugin.processor.minAllowedMessageKind` > annotation processor option to `PluginProcessor` to filter > diagnostic messages by severity. This allows builds that > treat compiler notes as errors (e.g. Maven with `-Werror`) > to suppress informational notes emitted during normal > plugin processing. (#3380, #4063) > * Add missing setters to `Rfc5424LayoutBuilder` > > === Changed > > * Ensure scripts in the global `Scripts` element have > explicit names by throwing a `ConfigurationException` > for unnamed ones. (#3176) > * Simplify file manager registry factory methods (#3968) > > === Deprecated > > * Deprecated withers in builder classes in favor of setters. > This change improves API consistency with Log4j Core > 3 and helps users adapt to the upcoming changes. (#3750) > > === Fixed > > * Fix script resolution failure when the `Scripts` element > is placed after a `ScriptRef` in the configuration. (#3336) > * Fix `ArrayIndexOutOfBoundsException` thrown by > `ThrowableStackTraceRenderer` when the stack trace > is modified concurrently (#3940, #3955) > * Fix `SLF4JLogger.atFatal()` returning `atLevel(Level.TRACE)` > instead of `atLevel(Level.FATAL)`. This was causing > `FATAL`-level log events to be silently discarded when using > the fluent API through the `log4j-to-slf4j` bridge. (#4068, #4089) > * Fix Javadoc references across module boundaries > (i.e., cross-references) (#4099, #4100) > * Fix header write in `RollingRandomAccessFileManager` that > was being incorrectly skipped if `append=true` and the file > didn't exist before > * Fix a properties file configuration regression caused by not > referenced loggers, appenders, and filters (#4036, #4069) > > === Removed > > * Remove the `jvmrunargs` lookup. (#3874) > > === Updated > > * Update `org.junit:junit-bom` to version `5.13.4` (#3850) > * Update `org.mongodb:bson` to version `5.6.1` (#3961) > * Update `org.xerial.snappy:snappy-java` to version `1.1.10.8` (#3841)
