This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/springVersion-5.3.20
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
discard 2e6fee340d Bump springVersion from 5.3.19 to 5.3.20
add 30a5f51acc Bump jackson2Version from 2.13.2 to 2.13.3
add 06511c6e46 Bump maven-clean-plugin from 3.1.0 to 3.2.0
add 0b2ad4b71f Bump docker-maven-plugin from 0.39.0 to 0.39.1
add c7dbe45be3 Bump maven-resources-plugin from 3.0.2 to 3.2.0
add fb5ee513fb Bump de.flapdoodle.embed.mongo from 3.4.5 to 3.4.6
add 022802aa3c Bump kubernetes-client from 5.12.1 to 5.12.2
add 70cfb74bbd Bump springVersion from 5.3.19 to 5.3.20
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 (2e6fee340d)
\
N -- N -- N refs/heads/dependabot/maven/springVersion-5.3.20
(70cfb74bbd)
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-spring-cloud-config-sample-server/pom.xml | 2 +-
pom.xml | 12 ++++++------
2 files changed, 7 insertions(+), 7 deletions(-)
