dependabot[bot] opened a new pull request, #593:
URL: https://github.com/apache/opennlp-sandbox/pull/593

   Bumps [org.docx4j:docx4j-core](https://github.com/plutext/docx4j) from 
11.5.14 to 17.3.2.
   <details>
   <summary>Changelog</summary>
   <p><em>Sourced from <a 
href="https://github.com/plutext/docx4j/blob/VERSION_17_3_3/CHANGELOG.md";>org.docx4j:docx4j-core's
 changelog</a>.</em></p>
   <blockquote>
   <h1>Version 17.3.2</h1>
   <h2>Release date</h2>
   <p>9 October 2026</p>
   <h2>Contributors to this release</h2>
   <p>Jason Harrop</p>
   <p>Claude Fable 5.1 and Opus 5.5</p>
   <h2>Changes in Version 17.3.2</h2>
   <p>Digital signatures (new module docx4j-digsig, formerly Plutext 
DigSig):</p>
   <ul>
   <li>Sign a docx, pptx or xlsx (XML-DSig, XAdES-EPES or XAdES-T, SHA-256 by 
default) so that
   Word, Excel and PowerPoint report a valid signature; validate signatures 
made by Office
   or by docx4j.</li>
   <li>Documentation: docs/docx4j_DigitalSignatures.docx (the user guide: 
signing, visible
   signatures in Word and Excel, validation, trust checking, limitations, test 
certificates)
   and docs/DigitalSignatures.md (the per-format support statement and what was 
checked in
   Office).</li>
   <li>docx4j-core: a part class that lives in another module is now found 
through the
   PartProvider service (org.docx4j.openpackaging.parts.PartProvider, 
uses/provides) instead
   of Class.forName; docx4j-digsig provides the signature parts.  The 
module-info also
   declares <code>uses</code> for MetafileSvgProvider, without which that 
lookup failed on the module
   path.</li>
   </ul>
   <p>PDF via XSL FO:</p>
   <ul>
   <li>
   <p>docx4j-fo-renderer 2.11-docx4j.6 (was .5): the hooks the rules of this 
release need, including
   for section columns of unequal width</p>
   </li>
   <li>
   <p>for other improvements, see  <a 
href="https://github.com/plutext/docx4j/blob/8faf6e356c399b077890f34251d17746c88442d4/CHANGELOG.md";>https://github.com/plutext/docx4j/blob/8faf6e356c399b077890f34251d17746c88442d4/CHANGELOG.md</a></p>
   </li>
   </ul>
   <h1>Version 17.3.1</h1>
   <h2>Release date</h2>
   <p>7 October 2026</p>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/plutext/docx4j/commit/856afc5dace914815b6092fd549bc28e5ba7014d";><code>856afc5</code></a>
 prepare for 17.3.2 release</li>
   <li><a 
href="https://github.com/plutext/docx4j/commit/8faf6e356c399b077890f34251d17746c88442d4";><code>8faf6e3</code></a>
 CHANGELOG: docx4j-digsig documentation and the PartProvider service</li>
   <li><a 
href="https://github.com/plutext/docx4j/commit/78baa9341dabafb0fef12b7f862f611198e7398e";><code>78baa93</code></a>
 docs: docx4j_DigitalSignatures.docx, user documentation for docx4j-digsig</li>
   <li><a 
href="https://github.com/plutext/docx4j/commit/409392c9a034e47579d6f748615d40c2adafd4fb";><code>409392c</code></a>
 docx4j-export-fo depends on docx4j-fo-renderer 2.11-docx4j.6 (was .5), gated 
...</li>
   <li><a 
href="https://github.com/plutext/docx4j/commit/97a3020f33defa50c672ed4f8ab51419e021d57b";><code>97a3020</code></a>
 CR-033: template.potx in the corpus, its 555 KB image replaced</li>
   <li><a 
href="https://github.com/plutext/docx4j/commit/458b32891a87ab9e84214642fb79345305f7f8c8";><code>458b328</code></a>
 CR-033 done: Office check passed, phase 4 record</li>
   <li><a 
href="https://github.com/plutext/docx4j/commit/19ec762eeb640b8582f6fe7f51c1578c3a6a5128";><code>19ec762</code></a>
 CR-033 phase 2 review: PartProviders package-private; uses 
MetafileSvgProvider</li>
   <li><a 
href="https://github.com/plutext/docx4j/commit/12b3530ca3b1a6c9e8edf03359801a521e8146a2";><code>12b3530</code></a>
 CR-033 phase 2: PartProvider service; phase 3 documentation</li>
   <li><a 
href="https://github.com/plutext/docx4j/commit/df1e535b14a62e7ea0a4e1e9fe31cc547faf9777";><code>df1e535</code></a>
 CR-033 phase 1: digital signatures as module docx4j-digsig</li>
   <li><a 
href="https://github.com/plutext/docx4j/commit/c8a6094ead4a434b91e87b8f95b6fb00a056ae15";><code>c8a6094</code></a>
 Keep chains: the closing break's width counted, a segment ending at a 
table's...</li>
   <li>Additional commits viewable in <a 
href="https://github.com/plutext/docx4j/compare/docx4j-11.5.14...docx4j-17.3.2";>compare
 view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.docx4j:docx4j-core&package-manager=maven&previous-version=11.5.14&new-version=17.3.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   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