This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/de.javakaffee-kryo-serializers-0.45
in repository https://gitbox.apache.org/repos/asf/dubbo.git
omit 35b245d91a Bump kryo-serializers from 0.42 to 0.45
add 937dcfedbb Bump xmemcached from 1.3.6 to 1.4.3 (#11486)
add b14de22b16 Bump maven-failsafe-plugin from 3.0.0-M5 to 3.0.0-M8
(#11485)
add e327f8ff7c Bump maven-release-plugin from 3.0.0-M1 to 3.0.0-M7 (#11484)
add ef7c5187a4 Bump mockito-junit-jupiter from 3.8.0 to 3.12.4 (#11483)
add 327d2cd6ad Bump api from 0.1.23 to 0.1.35 (#11482)
add e2283b7914 Bump netty from 3.2.5.Final to 3.2.10.Final (#11481)
add 62e5ff1faf Bump bytebuddy.version from 1.12.22 to 1.12.23 (#11480)
add 23a7bd967e Bump fst from 2.48-jdk-6 to 2.57 (#11478)
add f6ab287d27 Bump kryo-serializers from 0.42 to 0.45
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 (35b245d91a)
\
N -- N -- N
refs/heads/dependabot/maven/de.javakaffee-kryo-serializers-0.45 (f6ab287d27)
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-dependencies-bom/pom.xml | 8 ++++----
dubbo-kubernetes/pom.xml | 2 +-
dubbo-spring-boot/pom.xml | 2 +-
pom.xml | 4 ++--
4 files changed, 8 insertions(+), 8 deletions(-)
