This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a change to branch
automated/upgrade-docling-container-v1.30.0-fixed
in repository https://gitbox.apache.org/repos/asf/camel.git
omit 80191df7192f chore(camel-test-infra-docling): upgrade
docling.container to v1.30.0
add 5dabc378f342 chore(camel-test-infra-milvus): upgrade milvus.container
to v2.6.22 (#25470)
add c67e658970cd chore(camel-test-infra-docling): upgrade
docling.container to v1.30.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 (80191df7192f)
\
N -- N -- N
refs/heads/automated/upgrade-docling-container-v1.30.0-fixed (c67e658970cd)
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:
.../org/apache/camel/test/infra/milvus/services/container.properties | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
