This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/io.swagger.core.v3-swagger-core-jakarta-2.2.28
in repository https://gitbox.apache.org/repos/asf/servicecomb-java-chassis.git
omit f009b0299 Bump io.swagger.core.v3:swagger-core-jakarta from 2.2.27 to
2.2.28
add 5055d1a34 [#4690] fixed mixin-maven-plugin not work with maven 3.9.9+
and 4.0.0+ problem (#4707)
add be10defda Bump io.zipkin.zipkin2:zipkin from 3.4.3 to 3.4.4 (#4705)
add 74137b28e Bump com.puppycrawl.tools:checkstyle from 10.21.1 to 10.21.2
(#4703)
add d17101ed5 Bump org.kiwiproject:consul-client from 1.4.2 to 1.4.5
(#4702)
add 80efa4ba8 Bump org.assertj:assertj-core from 3.27.0 to 3.27.3 (#4701)
add 41c2b56cc Bump org.owasp:dependency-check-maven from 11.1.1 to 12.0.2
(#4700)
add 95d3cbc47 Bump vertx.version from 4.5.11 to 4.5.12 (#4691)
add 6b3c85af4 Bump io.swagger.core.v3:swagger-core-jakarta from 2.2.27 to
2.2.28
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 (f009b0299)
\
N -- N -- N
refs/heads/dependabot/maven/io.swagger.core.v3-swagger-core-jakarta-2.2.28
(6b3c85af4)
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:
.github/workflows/maven.yml | 4 ++++
dependencies/default/pom.xml | 8 ++++----
pom.xml | 4 ++--
3 files changed, 10 insertions(+), 6 deletions(-)
