Bump org.tukaani:xz from 1.10 to 1.11 in /plugins/ingest-attachment

[dependabot]

Bumps org.tukaani:xz from 1.10 to 1.11.

Changelog

Sourced from org.tukaani:xz's changelog.

1.11 (2025-11-19)

• Fix a data corruption bug when encoding with the rarely-used option LZMA2Options.MODE_UNCOMPRESSED. To trigger the bug, a write call must cross an offset that is a multiple of 65536 bytes. For example, one write of 70000 bytes or two write calls of 50000 bytes each would trigger the bug. The bug isn't triggered if there are ten write calls of 8192 bytes each followed by one 123-byte write.

  If encoding to a .xz file, a decoder would catch the issue because the integrity check wouldn't match.

• The binaries of 1.10 in the Maven Central require Java 8 and contain optimized classes for Java >= 9 as multi-release JAR. They were built with OpenJDK 21.0.9 on GNU/Linux and can be reproduced using the following command:

  SOURCE_DATE_EPOCH=1763575020 TZ=UTC0 ant maven
  

Commits

• eec2ad9 Bump the version number to 1.11
• cd59206 Update NEWS.md for 1.11
• afd20a2 Omit the .github directory from releases
• 061ba5d CI: Add Coverity Scan
• cc7ea2e UncompressedLZMA2OutputStream: Don't mention ResettableArrayCache
• 6dd6e27 LZMACoder: Fix a copy-paste error
• d010bdf IA64.code: Silence a false positive from Coverity
• 2ff3ec5 REUSE.toml: Bump REUSE spec version from 3.2 to 3.3
• 14c7102 REUSE.toml: Add SHA256SUMS
• 74e42f4 Avoid an unneeded arraycopy in UncompressedLZMA2OutputStream
• Additional commits viewable in compare view

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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

[github-actions]

❌ Gradle check result for fc45024: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 56d6a22: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for c40c3e2: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for c40c3e2: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for c40c3e2: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for c40c3e2: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

✅ Gradle check result for c40c3e2: SUCCESS

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.33%. Comparing base (97d3864) to head (c40c3e2).
⚠️ Report is 9 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main   #20082      +/-   ##
============================================
- Coverage     73.33%   73.33%   -0.01%     
+ Complexity    71679    71675       -4     
============================================
  Files          5790     5790              
  Lines        327549   327661     +112     
  Branches      47181    47204      +23     
============================================
+ Hits         240217   240291      +74     
+ Misses        68080    68022      -58     
- Partials      19252    19348      +96     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.