This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/io.milvus-milvus-sdk-java-2.5.0
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 89b84d0fc79 chore(deps): Bump io.milvus:milvus-sdk-java from 2.4.8 to
2.5.0
add 9186e27f7d8 chore(deps): Bump grpc-version from 1.68.1 to 1.68.2
(#16400)
add d3f9e35b688 chore(deps): Bump org.mybatis:mybatis from 3.5.16 to
3.5.17 (#16402)
add c6d9ec6a2b1 chore(deps): Bump debezium-version from 3.0.3.Final to
3.0.4.Final (#16404)
add f09b4f2c9e3 chore(deps): Bump huaweicloud-sdk-version from 3.1.123 to
3.1.124 (#16405)
add 656a8b4c6e2 chore(deps): Bump io.milvus:milvus-sdk-java from 2.4.8 to
2.5.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 (89b84d0fc79)
\
N -- N -- N
refs/heads/dependabot/maven/io.milvus-milvus-sdk-java-2.5.0 (656a8b4c6e2)
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:
parent/pom.xml | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
