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.2.0
in repository https://gitbox.apache.org/repos/asf/dubbo.git
omit 2cd483ca12 Bump io.micrometer:micrometer-tracing-bom from 1.1.6 to
1.2.0
add cf5f9db785 Bump protobuf-java_version from 3.25.0 to 3.25.1 (#13394)
add dae5b1cf46 Bump io.projectreactor:reactor-core from 3.5.11 to 3.6.0
(#13391)
add aff714e5bb Bump jackson_version from 2.15.3 to 2.16.0 (#13388)
add 77bf43d40c Bump org.testcontainers:testcontainers from 1.19.1 to
1.19.2 (#13389)
add 6378c144f8 Bump io.opentelemetry:opentelemetry-bom from 1.31.0 to
1.32.0 (#13392)
add 883195aeb9 Bump io.micrometer:micrometer-bom from 1.11.5 to 1.12.0
(#13395)
new 304f44bb6b Bump io.micrometer:micrometer-tracing-bom from 1.1.6 to
1.2.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 (2cd483ca12)
\
N -- N -- N
refs/heads/dependabot/maven/io.micrometer-micrometer-tracing-bom-1.2.0
(304f44bb6b)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
dubbo-config/dubbo-config-api/pom.xml | 2 +-
dubbo-dependencies-bom/pom.xml | 10 +++++-----
.../dubbo-spring-boot-starters/observability/pom.xml | 4 ++--
3 files changed, 8 insertions(+), 8 deletions(-)
