This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/main/net.javacrumbs.json-unit-json-unit-4.1.1
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
omit 1f451f0f8e Bump net.javacrumbs.json-unit:json-unit from 4.1.0 to 4.1.1
add aa0aa26366 Update `com.google.code.gson:gson` to version `2.13.1`
(#3636) (#3636)
add c1f670e32d Update `org.wiremock:wiremock` to version `3.13.0` (#3637)
(#3637)
add b75dd4ad49 Update `org.springframework.boot:spring-boot-autoconfigure`
to version `3.4.5` (#3640) (#3640)
add e6653d4044 Update `com.fasterxml.jackson:jackson-bom` to version
`2.19.0` (#3641) (#3641)
add 5733f06060 Bump net.javacrumbs.json-unit:json-unit from 4.1.0 to 4.1.1
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 (1f451f0f8e)
\
N -- N -- N
refs/heads/dependabot/maven/main/net.javacrumbs.json-unit-json-unit-4.1.1
(5733f06060)
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:
log4j-core-test/pom.xml | 4 ++--
log4j-parent/pom.xml | 2 +-
log4j-spring-cloud-config-client/pom.xml | 2 +-
src/changelog/.3.x.x/update_com_fasterxml_jackson_jackson_bom.xml | 4 ++--
src/changelog/.3.x.x/update_com_google_code_gson_gson.xml | 4 ++--
.../update_org_springframework_boot_spring_boot_autoconfigure.xml | 4 ++--
src/changelog/.3.x.x/update_org_wiremock_wiremock.xml | 4 ++--
7 files changed, 12 insertions(+), 12 deletions(-)
