ok, i will start the process On Wed, Jun 24, 2026 at 5:07 PM Volkan Yazıcı <[email protected]> wrote:
> #4146 has API changes, it cannot go to a patch release. If you disagree, > please explain. > > #4142 still needs to be reviewed. `2.26.1` can be shipped with or without > it, both are fine. But it should not be a blocker for `2.26.1`. > > Ramanathan, you can create the `2.26.x` branch from the `rel/2.26.0` tag, > and copy `.github/dependabot.yaml` changes from the `2.25.x` branch, > assuming Piotr already updated that to perform PATCH-level upgrades as he > suggested. > > On Wed, Jun 24, 2026 at 11:27 AM Piotr P. Karwasz < > [email protected]> > wrote: > > > > > Hi Ramanathan, > > > > On 24.06.2026 10:12, Ramanathan Muthu wrote: > > > Please let me know if there are any additional changes or concerns > > > before we proceed. > > > > > > Your small fixes for the `*.properties` configuration format look like > > something you could also add: > > > > https://github.com/apache/logging-log4j2/pull/4116 > > https://github.com/apache/logging-log4j2/pull/4142 > > > > Bumping our dependencies to the latest patch version, might be also a > > good idea. On 2.x Dependabot is configured to perform any kind of > > upgrades, but you could create a 2.26.x branch first and configure > > Dependabot to perform PATCH level upgrades. > > > > Piotr > > >
