Update xz to 1.11

[xerial-bot]

About this PR

📦 Updates org.tukaani:xz from 1.10 to 1.11

📜 GitHub Release Notes - Version Diff

Usage

✅ Please merge!

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

🔍 Files still referring to the old version number

The following files still refer to the old version number (1.10).
You might want to review and update them manually.

ReleaseNotes.md
sbt
src/sbt-test/sbt-pack/jvm-version-opts/project/build.properties

⚙ Adjust future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "org.tukaani", artifactId = "xz" } ]

Or, add this to slow down future updates of this dependency:

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.tukaani", artifactId = "xz" }
}]

^{labels: library-update, old-version-remains, commit-count:1}

[gemini-code-assist]

Summary of Changes

Hello @xerial-bot, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request aims to upgrade the org.tukaani:xz library to its latest version, 1.11. This update ensures the project benefits from the most recent improvements and fixes provided by the library, maintaining up-to-date dependencies and enhancing overall stability.

Highlights

• Dependency Update: The org.tukaani:xz library has been updated from version 1.10 to 1.11.
• Potential Manual Updates: Files such as ReleaseNotes.md, sbt, and src/sbt-test/sbt-pack/jvm-version-opts/project/build.properties may still reference the old version and might require manual review.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the org.tukaani:xz dependency from version 1.10 to 1.11. This is a safe and recommended update, as version 1.11 is a bug-fix release. It's worth noting that this Java library is not affected by the recent backdoor found in the xz-utils C library. The change in build.sbt is correct. As noted by Scala Steward in the pull request description, you may want to manually review other files that might still refer to the old version.