This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/io.micrometer-micrometer-bom-1.12.3
in repository https://gitbox.apache.org/repos/asf/dubbo.git
discard 63ec4259ab Bump io.micrometer:micrometer-bom from 1.12.2 to 1.12.3
add 5e1d333ce6 Bump io.micrometer:micrometer-core from 1.12.2 to 1.12.3
(#13760)
add d7ada39797 Bump net.bytebuddy:byte-buddy from 1.14.11 to 1.14.12
(#13761)
add 11a9de26e1 Bump io.micrometer:micrometer-tracing-bom from 1.2.2 to
1.2.3 (#13762)
add 685c5e50e7 Bump protobuf-java_version from 3.25.2 to 3.25.3 (#13763)
add faa2e9abb2 Bump org.apache.commons:commons-compress from 1.25.0 to
1.26.0 (#13765)
add 9e59f3a18e Bump io.micrometer:micrometer-bom from 1.12.2 to 1.12.3
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 (63ec4259ab)
\
N -- N -- N
refs/heads/dependabot/maven/io.micrometer-micrometer-bom-1.12.3 (9e59f3a18e)
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:
dubbo-demo/dubbo-demo-spring-boot/pom.xml | 2 +-
dubbo-dependencies-bom/pom.xml | 8 ++++----
.../dubbo-spring-boot-starters/observability/pom.xml | 2 +-
dubbo-test/dubbo-test-check/pom.xml | 2 +-
4 files changed, 7 insertions(+), 7 deletions(-)
