This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/io.micrometer-micrometer-tracing-bom-1.1.1
in repository https://gitbox.apache.org/repos/asf/dubbo.git
discard 20940055aa Bump micrometer-tracing-bom from 1.0.4 to 1.1.1
add cbc2040133 Update zk version (#12319)
add 01d0816b4c Bump micrometer-bom from 1.10.6 to 1.11.0 (#12313)
add beeae06ccc Bump reactor-core from 3.5.5 to 3.5.6 (#12312)
add 50272d1e46 Bump native-maven-plugin from 0.9.21 to 0.9.22 (#12311)
add 171e361a4d Bump build-helper-maven-plugin from 3.3.0 to 3.4.0 (#12310)
add 7ee716475c Bump micrometer-tracing-bom from 1.0.4 to 1.1.1
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 (20940055aa)
\
N -- N -- N
refs/heads/dependabot/maven/io.micrometer-micrometer-tracing-bom-1.1.1
(7ee716475c)
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:
.../apache/dubbo/config/spring/isolation/api/ApiIsolationTest.java | 3 +++
dubbo-demo/dubbo-demo-native/dubbo-demo-native-consumer/pom.xml | 2 +-
dubbo-demo/dubbo-demo-native/dubbo-demo-native-provider/pom.xml | 2 +-
dubbo-dependencies-bom/pom.xml | 4 ++--
dubbo-spring-boot/dubbo-spring-boot-observability-starters/pom.xml | 2 +-
pom.xml | 2 +-
6 files changed, 9 insertions(+), 6 deletions(-)
