This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/vertx.version-4.5.7
in repository https://gitbox.apache.org/repos/asf/servicecomb-java-chassis.git
discard e20ed86e3 Bump vertx.version from 4.4.8 to 4.5.7
add 95e117d92 Bump org.apache.maven.plugins:maven-compiler-plugin (#4280)
add 3838cd7c3 Bump io.swagger.core.v3:swagger-core-jakarta from 2.2.20 to
2.2.21 (#4279)
add e3755e12d Bump vertx.version from 4.4.8 to 4.5.7
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 (e20ed86e3)
\
N -- N -- N refs/heads/dependabot/maven/vertx.version-4.5.7
(e3755e12d)
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 | 2 +-
pom.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
