Skip to content

Bump tika.version from 3.3.0 to 4.0.0 - #19

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/maven/tika.version-4.0.0
Open

dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/maven/tika.version-4.0.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 14, 2026

Copy link
Copy Markdown

Bumps tika.version from 3.3.0 to 4.0.0.
Updates org.apache.tika:tika-core from 3.3.0 to 4.0.0

Changelog

Sourced from org.apache.tika:tika-core's changelog.

Release 4.1.0 - unreleased

  • A text recognizer is an engine: configure Tesseract, Tess4J or a VLM once under "engines" and name it from "text-recognizers" with {"engine": ""} (plus _mime-include/_mime-exclude). The 4.0 form with the engine inline still works. An inference binding cannot use a recognizer for a task it does not fit (TIKA-4889).

  • PAGES input for inference bindings: pdf-parser.inference.input lists what the PDF releases (TEXT by default; PAGES renders every page for a PAGES binding). One render per page feeds OCR and the bindings, and each page's vector lands on the PDF with a page locator. A page render emitted as an embedded document is no longer an IMAGES unit. OCR_ONLY annotated an OCR'd page twice when pages were rendered as embedded documents; once now (TIKA-4889).

  • New "inference" config section: bind a named engine to an input (IMAGES) and tasks (embed), and every image document Tika parses is embedded in one request per document tree; vectors land on the document the image belongs to, as it appears in the output. Per request, "inference" in parse-context selects bindings or switches inference off. openai-image-embedding-parser keeps working, one request per image (TIKA-4889).

  • New "engines" config section: a map of names to inference engines, each an endpoint or local binary with its settings (openai-embedding-engine posts up to maxBatchSize images per request to an OpenAI-compatible /v1/embeddings). Engines are called by the inference bindings that follow; nothing calls them yet (TIKA-4889).

  • The image embedder writes a picture's vector onto the document the picture appears in (INLINE and RENDERING children) with an "embedded" locator naming the picture; attachments keep their own, and liftToParent: false keeps every picture's vector on the picture. RecursiveParserWrapper exposes the parent's Metadata to a child's parse as ParentMetadata, and ChunkTarget (tika-inference) resolves where a child's chunks land (TIKA-4888).

  • A PDF page rendered as an embedded document (imageStrategy RENDER_PAGES_*) is enriched once, by the PDF parser: the text recognizer where the OCR strategy says so, every other text-recognizers entry on every page, results on the PDF itself. The embedded copy is no longer enriched again by image-parser, so an image embedder no longer yields two vectors for a text-poor page and Tesseract no longer OCRs a page twice; NO_OCR now means no page OCR at all. ContentEnrichers gains scoped suspend and suspendRecognizers for containers that enrich their own renderings (TIKA-4887).

  • OCR engines and other content enrichers: name the engine in "text-recognizers" and every default parser stays loaded; "text-recognizers": [] turns enrichment

... (truncated)

Commits
  • 514e1b3 [maven-release-plugin] prepare release 4.0.0-rc1
  • 4e39e07 revert second rc1 attempt
  • 7975986 javadocs take 42
  • 95d4235 [maven-release-plugin] prepare for next development iteration
  • 666289b [maven-release-plugin] prepare release 4.0.0-rc1
  • c9f6585 TIKA-4808 - revert aborted 4.0.0-rc1 release commits; fix per-module javadoc ...
  • 41183e7 [maven-release-plugin] prepare for next development iteration
  • 5dd7fc7 [maven-release-plugin] prepare release 4.0.0-rc1
  • 4b231cf TIKA-4808 -- prep CHANGES.txt for release
  • 532a685 TIKA-4808 - remove access to the network parser from cli (#3036)
  • Additional commits viewable in compare view

Updates org.apache.tika:tika-parsers-standard-package from 3.3.0 to 4.0.0

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps `tika.version` from 3.3.0 to 4.0.0.

Updates `org.apache.tika:tika-core` from 3.3.0 to 4.0.0
- [Changelog](https://github.com/apache/tika/blob/main/CHANGES.txt)
- [Commits](apache/tika@3.3.0...4.0.0)

Updates `org.apache.tika:tika-parsers-standard-package` from 3.3.0 to 4.0.0

---
updated-dependencies:
- dependency-name: org.apache.tika:tika-core
  dependency-version: 4.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
- dependency-name: org.apache.tika:tika-parsers-standard-package
  dependency-version: 4.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file java Pull requests that update java code labels Sep 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file java Pull requests that update java code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants