This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/spring-boot.version-3.4.4
in repository https://gitbox.apache.org/repos/asf/servicecomb-java-chassis.git
discard f85ab5421 Bump spring-boot.version from 3.3.5 to 3.4.4
add 59b8851dc [#4779] add filter by SPIEnabled
add 1cfe7e6f0 Merge pull request #4780 from vikeria/master
add 8ce1d956e Bump com.google.guava:guava from 33.4.0-jre to 33.4.6-jre
(#4772)
add 963425a1c Bump com.alibaba.nacos:nacos-client from 2.4.3 to 2.5.1
(#4771)
add a62444689 Bump io.micrometer:micrometer-bom from 1.14.4 to 1.14.5
(#4770)
add 9d4f31585 Bump org.apache.maven.plugins:maven-failsafe-plugin from
3.5.2 to 3.5.3 (#4767)
add 8e4f7a94a Bump com.google.guava:failureaccess from 1.0.2 to 1.0.3
(#4766)
add 382ea0996 Bump org.apache.maven.plugins:maven-surefire-plugin from
3.5.2 to 3.5.3 (#4764)
add 30ecca8d5 Bump io.etcd:jetcd-core from 0.8.4 to 0.8.5 (#4762)
add 6f89a857a Bump spring-boot.version from 3.3.5 to 3.4.4
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 (f85ab5421)
\
N -- N -- N
refs/heads/dependabot/maven/spring-boot.version-3.4.4 (6f89a857a)
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 | 10 +++++-----
.../org/apache/servicecomb/registry/RegistrationManager.java | 3 ++-
pom.xml | 4 ++--
3 files changed, 9 insertions(+), 8 deletions(-)
