This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/log4j2.version-2.25.0
in repository https://gitbox.apache.org/repos/asf/servicecomb-java-chassis.git
discard 61c8c8122 Bump log4j2.version from 2.24.3 to 2.25.0
add 38ee9a1a3 Bump org.apache.maven:maven-model from 3.9.9 to 3.9.10
(#4872)
add 91905af4d Bump com.github.spotbugs:spotbugs-maven-plugin from 4.9.3.0
to 4.9.3.2 (#4871)
add 5304336ec Bump com.alibaba.nacos:nacos-client from 3.0.1 to 3.0.2
(#4869)
add d46003341 Bump log4j2.version from 2.24.3 to 2.25.0
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 (61c8c8122)
\
N -- N -- N refs/heads/dependabot/maven/log4j2.version-2.25.0
(d46003341)
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:
dependencies/default/pom.xml | 4 ++--
pom.xml | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
