Skip to content

chore(camel-test-infra-docling): upgrade docling.container to v1.30.0 - #25471

Merged
davsclaus merged 2 commits into
mainfrom
automated/upgrade-docling-container-v1.30.0-fixed
Aug 12, 2026
Merged

chore(camel-test-infra-docling): upgrade docling.container to v1.30.0#25471
davsclaus merged 2 commits into
mainfrom
automated/upgrade-docling-container-v1.30.0-fixed

Conversation

@davsclaus

Copy link
Copy Markdown
Contributor

Summary

  • Upgrade docling container from v1.29.0 to v1.30.0
  • Update OcrExtractionIT.testOcrWithMultipleTextBlocks sentinel assertion: docling v1.30.0 now includes page furniture (headers/footers) in the default body export, so the test now asserts footer text is present (was previously asserting it was absent)
  • Update documentation note in docling-component.adoc to reflect the new behavior

Supersedes #25417 which had merge conflicts. Addresses the behavioral change flagged by @gnodet's local IT results.

Test plan

  • CI build passes
  • Integration tests with docling v1.30.0 pass (the OCR test assertion is updated to match new behavior)

Claude Code on behalf of davsclaus

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com

@github-actions

Copy link
Copy Markdown
Contributor

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

  • First-time contributors require MANUAL approval for the GitHub Actions to run
  • You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
  • You can label PRs using skip-tests and test-dependents to fine-tune the checks executed by this PR.
  • Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

Since docling v1.30.0, page furniture (headers/footers) is included in
the default body export. Update the sentinel test assertion in
OcrExtractionIT to expect this new behavior and update the documentation
note accordingly.

Supersedes #25417.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Claus Ibsen <claus.ibsen@gmail.com>
@davsclaus
davsclaus force-pushed the automated/upgrade-docling-container-v1.30.0-fixed branch from 80191df to c67e658 Compare August 12, 2026 15:51
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Claus Ibsen <claus.ibsen@gmail.com>
@github-actions

Copy link
Copy Markdown
Contributor

🧪 CI tested the following changed modules:

  • catalog/camel-catalog
  • components/camel-ai/camel-docling
  • test-infra/camel-test-infra-all
  • test-infra/camel-test-infra-docling

🔬 Scalpel shadow comparison — Scalpel: 12 tested, 28 compile-only — current: 11 all tested

Maveniverse Scalpel detected 40 affected modules (current approach: 11).

⚠️ Modules only in Scalpel (29)
  • apache-camel
  • camel-allcomponents
  • camel-catalog
  • camel-catalog-console
  • camel-catalog-lucene
  • camel-catalog-maven
  • camel-catalog-suggest
  • camel-componentdsl
  • camel-csimple-maven-plugin
  • camel-endpointdsl
  • camel-endpointdsl-support
  • camel-itest
  • camel-jbang-core
  • camel-jbang-it
  • camel-jbang-main
  • camel-jbang-plugin-edit
  • camel-jbang-plugin-generate
  • camel-jbang-plugin-kubernetes
  • camel-jbang-plugin-test
  • camel-kamelet-main
  • camel-launcher
  • camel-report-maven-plugin
  • camel-route-parser
  • camel-yaml-dsl
  • camel-yaml-dsl-deserializers
  • camel-yaml-dsl-maven-plugin
  • coverage
  • docs
  • dummy-component

Skip-tests mode would test 12 modules (4 direct + 8 downstream), skip tests for 28 (generated code, meta-modules)

Modules Scalpel would test (12)
  • camel-catalog
  • camel-docling
  • camel-jbang-mcp
  • camel-jbang-plugin-mcp
  • camel-jbang-plugin-route-parser
  • camel-jbang-plugin-tui
  • camel-jbang-plugin-validate
  • camel-launcher-container
  • camel-test-infra-all
  • camel-test-infra-docling
  • camel-yaml-dsl-validator
  • camel-yaml-dsl-validator-maven-plugin
Modules with tests skipped (28)
  • apache-camel
  • camel-allcomponents
  • camel-catalog-console
  • camel-catalog-lucene
  • camel-catalog-maven
  • camel-catalog-suggest
  • camel-componentdsl
  • camel-csimple-maven-plugin
  • camel-endpointdsl
  • camel-endpointdsl-support
  • camel-itest
  • camel-jbang-core
  • camel-jbang-it
  • camel-jbang-main
  • camel-jbang-plugin-edit
  • camel-jbang-plugin-generate
  • camel-jbang-plugin-kubernetes
  • camel-jbang-plugin-test
  • camel-kamelet-main
  • camel-launcher
  • camel-report-maven-plugin
  • camel-route-parser
  • camel-yaml-dsl
  • camel-yaml-dsl-deserializers
  • camel-yaml-dsl-maven-plugin
  • coverage
  • docs
  • dummy-component

ℹ️ Shadow mode — Scalpel observes but does not affect test execution. Learn more

⚠️ Some tests are disabled on GitHub Actions (@DisabledIfSystemProperty(named = "ci.env.name")) and require manual verification:

  • components/camel-ai/camel-docling: 6 test(s) disabled on GitHub Actions
All tested modules (40 modules)
  • Camel :: AI :: Docling
  • Camel :: All Components Sync point
  • Camel :: Assembly
  • Camel :: Catalog :: CSimple Maven Plugin (deprecated)
  • Camel :: Catalog :: Camel Catalog
  • Camel :: Catalog :: Camel Report Maven Plugin
  • Camel :: Catalog :: Camel Route Parser
  • Camel :: Catalog :: Console
  • Camel :: Catalog :: Dummy Component
  • Camel :: Catalog :: Lucene (deprecated)
  • Camel :: Catalog :: Maven
  • Camel :: Catalog :: Suggest
  • Camel :: Component DSL
  • Camel :: Coverage
  • Camel :: Docs
  • Camel :: Endpoint DSL
  • Camel :: Endpoint DSL :: Support
  • Camel :: Integration Tests
  • Camel :: JBang :: Core
  • Camel :: JBang :: Integration tests
  • Camel :: JBang :: MCP
  • Camel :: JBang :: Main
  • Camel :: JBang :: Plugin :: Edit
  • Camel :: JBang :: Plugin :: Generate
  • Camel :: JBang :: Plugin :: Kubernetes
  • Camel :: JBang :: Plugin :: MCP
  • Camel :: JBang :: Plugin :: Route Parser
  • Camel :: JBang :: Plugin :: TUI
  • Camel :: JBang :: Plugin :: Testing
  • Camel :: JBang :: Plugin :: Validate
  • Camel :: Kamelet Main
  • Camel :: Launcher
  • Camel :: Launcher :: Container
  • Camel :: Test Infra :: All test services
  • Camel :: Test Infra :: Docling
  • Camel :: YAML DSL
  • Camel :: YAML DSL :: Deserializers
  • Camel :: YAML DSL :: Maven Plugins
  • Camel :: YAML DSL :: Validator
  • Camel :: YAML DSL :: Validator Maven Plugin

⚙️ View full build and test results

@gnodet gnodet left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clean container upgrade from docling-serve v1.29.0 to v1.30.0 with correctly adapted test assertion and documentation.

Verified:

  • Version bump follows established pattern (14+ prior docling container upgrades in git history).
  • The 36 deletions are fully justified: old documentation had a lengthy workaround section (referencing upstream issue #271, suggesting document restructuring) that is no longer needed since furniture is now included by default. Test similarly had explanatory comments replaced with shorter ones.
  • Container image (quay.io/docling-project/docling-serve:v1.30.0) hosted on quay.io (not Docker Hub), aligning with project convention.
  • Architecture support correctly handled: skipITs.s390x=true and skipITs.ppc64le=true already set (image only supports amd64/arm64).
  • Catalog copies and metadata.json consistently updated.
  • CI green on both JDK 17 and JDK 25.
  • The sentinel test pattern worked exactly as designed — the original assertFalse was documented as a canary that would fire when a future docling release includes page furniture. It fired, and this PR correctly responds.

One minor observation (non-blocking): The documentation states the furniture-layer inclusion is an intentional v1.30.0 feature, but the upstream docling-serve v1.30.0 release notes don't explicitly mention this change, and upstream issue docling-serve#271 for content-layer control remains open. The behavior is real (confirmed by IT results) but may be an undocumented side effect of other changes in bundled docling v2.118.0 rather than a guaranteed feature. Worth noting in case it gets reverted in a future release.

This review was generated by an AI agent and may contain inaccuracies. Please verify all suggestions before applying.

Claude Code on behalf of @gnodet

@davsclaus
davsclaus merged commit 49da32d into main Aug 12, 2026
6 checks passed
@davsclaus
davsclaus deleted the automated/upgrade-docling-container-v1.30.0-fixed branch August 12, 2026 17:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants