This is an automated email from the ASF dual-hosted git repository.
apupier pushed a change to branch
automated/upgrade-milvus-container-ppc64le-v2.6.5
in repository https://gitbox.apache.org/repos/asf/camel.git
omit 06c75e608560 chore(camel-test-infra-milvus): upgrade
milvus.container.ppc64le to v2.6.5
add b528331a6ba0 chore(camel-test-infra-mongodb): upgrade
mongodb.container to 7.0.31-jammy
add a0a099410450 chore(deps): Bump org.mnode.ical4j:ical4j from 4.2.3 to
4.2.4 (#22185)
add a5bfe0a81e34 chore(deps): Bump jackson2-version from 2.21.1 to 2.21.2
(#22183)
add b405a4e1c482 chore(deps): Bump aws-java-sdk2-version from 2.42.17 to
2.42.18
add 6d50e8641473 chore(camel-test-infra-milvus): upgrade
milvus.container.ppc64le to v2.6.5
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 (06c75e608560)
\
N -- N -- N
refs/heads/automated/upgrade-milvus-container-ppc64le-v2.6.5 (6d50e8641473)
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 | 6 +++---
.../apache/camel/test/infra/mongodb/services/container.properties | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
