This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/maven/2.26.x/maven-patch-updates-7a9876b81a
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
discard 1e03ee5d6f Bump the maven-patch-updates group with 31 updates
add 1352b98712 Fix handling of non-finite numbers while encoding
`MapMessage` to JSON (#4163)
add 3118122a00 Bump the maven-patch-updates group across 1 directory with
31 updates
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (1e03ee5d6f)
\
N -- N -- N
refs/heads/dependabot/maven/2.26.x/maven-patch-updates-7a9876b81a (3118122a00)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.../logging/log4j/message/MapMessageTest.java | 26 +++++++++++++++++++
.../log4j/message/MapMessageJsonFormatter.java | 30 +++++++++++++++++-----
.../fix-MapMessage-JSON-non-finite-number.xml} | 4 +--
3 files changed, 52 insertions(+), 8 deletions(-)
copy src/changelog/{2.25.2/3852-default-target.xml =>
.2.x.x/fix-MapMessage-JSON-non-finite-number.xml} (70%)
