This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/com.github.spotbugs-spotbugs-maven-plugin-4.7.0.0
in repository https://gitbox.apache.org/repos/asf/servicecomb-java-chassis.git
discard 3c5bcbe2b Bump spotbugs-maven-plugin from 4.6.0.0 to 4.7.0.0
add 4d0a93d14 [SCB-2523] Remove unused google code findbugs dependency
(#2980)
add ebb3cdd99 [SCB-2521] Optimize dependency management hibernate version
(#2978)
add 8b78d0190 Bump spotbugs-maven-plugin from 4.6.0.0 to 4.7.0.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 (3c5bcbe2b)
\
N -- N -- N
refs/heads/dependabot/maven/com.github.spotbugs-spotbugs-maven-plugin-4.7.0.0
(8b78d0190)
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 | 10 +---------
handlers/handler-loadbalance/pom.xml | 5 -----
2 files changed, 1 insertion(+), 14 deletions(-)
