dependabot[bot] opened a new pull request, #3663:
URL: https://github.com/apache/cxf/pull/3663

   Bumps `cxf.tika.version` from 4.1.0 to 4.2.0.
   Updates `org.apache.tika:tika-core` from 4.1.0 to 4.2.0
   <details>
   <summary>Changelog</summary>
   <p><em>Sourced from <a 
href="https://github.com/apache/tika/blob/main/CHANGES.txt";>org.apache.tika:tika-core's
 changelog</a>.</em></p>
   <blockquote>
   <p>Release 4.3.0 - ???</p>
   <p>BREAKING CHANGES AND DEPRECATIONS</p>
   <ul>
   <li>
   <p>FetcherManager.getFetcher and EmitterManager.getEmitter return a Lease
   (AbstractComponentManager.getComponent is now acquire); close it when done 
with
   the component and anything it returned. Pipes now closes a
   Closeable fetcher or emitter when a runtime save or delete replaces it 
(after the
   last task using it ends) and on graceful shutdown; nothing closed them 
before.
   EmittingUnpackHandler takes the emitter, not the EmitterManager 
(TIKA-5001).</p>
   </li>
   <li>
   <p>tika-grpc refuses SaveFetcher with configStoreType memory 
(FAILED_PRECONDITION):
   the forks never saw such a fetcher, so every fetch through it failed. Use 
file or
   ignite (TIKA-5001).</p>
   </li>
   </ul>
   <p>SERVER, PIPES AND OPERATIONS</p>
   <ul>
   <li>
   <p>tika-server no longer requires a &quot;server&quot; block in its config 
file; an absent block
   means the server defaults, as &quot;server&quot;: {} did. A tika-app config, 
or the documented
   Docker example { &quot;text-recognizers&quot;: [] }, now works as is 
(TIKA-XXXX).</p>
   </li>
   <li>
   <p>The tika-server full and tika-grpc Docker images no longer install
   ttf-mscorefonts-installer, which downloaded Microsoft's fonts from 
SourceForge
   at build time; non-embedded Verdana, Georgia, Trebuchet, Impact, Comic Sans 
and
   Arial Black now render with Liberation fonts. The images add the IPA and
   WenQuanYi fonts, so pages in non-embedded Japanese and Chinese fonts render
   instead of showing empty boxes or nothing (TIKA-5005).</p>
   </li>
   <li>
   <p>The S3 fetcher, emitter and pipes iterator accept credentialsProvider 
&quot;web_identity&quot;
   for EKS IAM roles for service accounts (IRSA); the plugin now bundles the 
AWS STS
   module it needs (TIKA-5006).</p>
   </li>
   <li>
   <p>tika-grpc applies parse-context.timeout-limits and exception-reporting in 
the server
   process too, so its backstop for a hung worker no longer falls back to the 
built-in
   timeouts. A FetchAndParse call interrupted before the parse finished (server 
shutdown)
   closes with UNAVAILABLE; a unary call used to fail with INTERNAL &quot;no 
value received&quot;,
   a server-streaming call completed with no reply, and a bidirectional stream 
went on
   to throw on the closed call. Thanks to Kristian Rickert and Davide Polato 
(TIKA-5010).</p>
   </li>
   <li>
   <p>The GCS fetcher, emitter and pipes iterator no longer require projectId. 
When it is
   unset, the client resolves a project from the environment, as it does for its
   credentials (TIKA-5009).</p>
   </li>
   <li>
   <p>The Kafka emitter reports success only once Kafka has acknowledged every 
record
   (per acks); a rejected or timed-out record fails the emit instead of being 
lost
   silently, and the producer is flushed and closed on shutdown. 
(TIKA-5008).</p>
   </li>
   <li>
   <p>The JDBC emitter is thread-safe: concurrent emits (shared-server mode, 
several
   async emitter threads) shared one connection and prepared statement 
unguarded,
   mixing values across rows and committing each other's batches 
(TIKA-5007).</p>
   </li>
   </ul>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/apache/tika/commit/91361891b61f6cc043a5ea81ced4867c17b93a9c";><code>9136189</code></a>
 [maven-release-plugin] prepare release 4.2.0-rc2</li>
   <li><a 
href="https://github.com/apache/tika/commit/872182e76695a90fbf6a169bcf20ffb5089139ab";><code>872182e</code></a>
 TIKA-4991 windows reset (<a 
href="https://redirect.github.com/apache/tika/issues/3417";>#3417</a>)</li>
   <li><a 
href="https://github.com/apache/tika/commit/e68fdf455a2fd3aa3d5449e1cd8a47221a144684";><code>e68fdf4</code></a>
 fix publish-docs (<a 
href="https://redirect.github.com/apache/tika/issues/3418";>#3418</a>)</li>
   <li><a 
href="https://github.com/apache/tika/commit/ec1882f3be4629ad5ca55f45a998415824d964b0";><code>ec1882f</code></a>
 [maven-release-plugin] prepare for next development iteration</li>
   <li><a 
href="https://github.com/apache/tika/commit/557418aaf533fe3f33142eb221bac18853273103";><code>557418a</code></a>
 [maven-release-plugin] prepare release 4.2.0-rc2</li>
   <li><a 
href="https://github.com/apache/tika/commit/3a40d6ccb1d282eca5638d2225d8c90ecca04059";><code>3a40d6c</code></a>
 update CHANGES.txt</li>
   <li><a 
href="https://github.com/apache/tika/commit/eb8d704c64fede93f6b8c10f2380c14f2a41304c";><code>eb8d704</code></a>
 revert to 4.2.0-SNAPSHOT (<a 
href="https://redirect.github.com/apache/tika/issues/3416";>#3416</a>)</li>
   <li><a 
href="https://github.com/apache/tika/commit/265c4a4199a682fc6d2169eab98646a9151ff107";><code>265c4a4</code></a>
 TIKA-4984 (<a 
href="https://redirect.github.com/apache/tika/issues/3415";>#3415</a>)</li>
   <li><a 
href="https://github.com/apache/tika/commit/6ab42aa835bfa7cfb13bbe8f57033f974c3e2f7a";><code>6ab42aa</code></a>
 TIKA-4991: wait for the body budget to drain between requests in 
MaxRequestSi...</li>
   <li><a 
href="https://github.com/apache/tika/commit/867344ffd1309b7e751e197b907fb0dcda19c79e";><code>867344f</code></a>
 [maven-release-plugin] prepare for next development iteration</li>
   <li>Additional commits viewable in <a 
href="https://github.com/apache/tika/compare/4.1.0...4.2.0";>compare 
view</a></li>
   </ul>
   </details>
   <br />
   
   Updates `org.apache.tika:tika-parser-pdf-module` from 4.1.0 to 4.2.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-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   <details>
   <summary>Dependabot commands and options</summary>
   <br />
   
   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)
   
   
   </details>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to