This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/io.zipkin.zipkin2-zipkin-3.1.0
in repository https://gitbox.apache.org/repos/asf/servicecomb-java-chassis.git
discard ac1f99807 Bump io.zipkin.zipkin2:zipkin from 2.26.0 to 3.1.0
add 077b84218 Bump org.junit:junit-bom from 5.10.1 to 5.10.2 (#4254)
add 53cc41f77 Bump log4j2.version from 2.22.1 to 2.23.0 (#4243)
add 237501d97 Bump org.codehaus.mojo:exec-maven-plugin from 3.1.1 to 3.2.0
(#4257)
add da7531fa8 Bump com.puppycrawl.tools:checkstyle from 10.13.0 to 10.14.0
(#4246)
add d33d683c2 [SCB-2864]upgrade vertx and fix connection pool problem and
enable log activity (#4261)
add 6f0437c9b Bump io.zipkin.zipkin2:zipkin from 2.26.0 to 3.1.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 (ac1f99807)
\
N -- N -- N
refs/heads/dependabot/maven/io.zipkin.zipkin2-zipkin-3.1.0 (6f0437c9b)
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 | 6 +-
.../vertx/client/http/HttpClientOptionsSPI.java | 3 +
pom.xml | 4 +-
.../client/HttpTransportHttpClientOptionsSPI.java | 5 +
.../rest/client/TransportClientConfig.java | 5 +
.../transport/rest/vertx/RestBodyHandler.java | 117 ++++++++++++---------
.../rest/vertx/MockHttpServerResponse.java | 6 ++
7 files changed, 94 insertions(+), 52 deletions(-)
