This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch dependabot/maven/aliyun-b5bd4c722c
in repository https://gitbox.apache.org/repos/asf/camel.git
omit 6c0be1e05d30 chore(deps): Bump the aliyun group with 2 updates
add f3dcac60c578 chore: fix spring-ai-image and docling CI failures by
switching to @DisabledIfEnvironmentVariable (#26142)
add 33b7377b16b4 chore: exclude transitive junit:junit 4.10 from
drill-jdbc in camel-drill
add e919d6506c72 Revert "chore(deps): Bump maven-surefire-plugin-version
from 3.5.6 to 3.6.0 (…"
add 5ec55ed47e55 chore(deps): Bump the aliyun group across 1 directory
with 2 updates
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 (6c0be1e05d30)
\
N -- N -- N refs/heads/dependabot/maven/aliyun-b5bd4c722c
(5ec55ed47e55)
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:
.../docling/integration/BatchProcessingIT.java | 4 +--
.../component/docling/integration/ChunkingIT.java | 4 +--
.../integration/DoclingServeProducerIT.java | 4 +--
.../integration/ExtractStructuredDataIT.java | 4 +--
.../docling/integration/MetadataExtractionIT.java | 4 +--
.../docling/integration/OcrExtractionIT.java | 4 +--
components/camel-drill/pom.xml | 4 +++
.../springai/image/SpringAiImageOllamaIT.java | 18 ++++++++++--
parent/pom.xml | 34 ++++++++++++++++++++++
pom.xml | 2 +-
10 files changed, 66 insertions(+), 16 deletions(-)
