Update airspec to 2025.1.24

[xerial-bot]

About this PR

📦 Updates org.wvlet.airframe:airspec from 2025.1.22 to 2025.1.24

📜 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!

⚙ Adjust future updates

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

updates.ignore = [ { groupId = "org.wvlet.airframe", artifactId = "airspec" } ]

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

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.wvlet.airframe", artifactId = "airspec" }
}]

^{labels: test-library-update, early-semver-patch, semver-spec-patch, 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 updates the airspec dependency in build.sbt from version 2025.1.22 to 2025.1.24. This is a patch update, and the PR was automatically generated by Scala Steward.

Highlights

• Dependency Update: This PR updates the airspec dependency from version 2025.1.22 to 2025.1.24.
• build.sbt Modification: The build.sbt file is modified to reflect the updated airspec version.
• Automated Update: This PR was automatically generated by Scala Steward. It will automatically resolve conflicts unless you modify it.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 airspec test library from version 2025.1.22 to 2025.1.24. The change is a straightforward dependency bump. My review includes a suggestion to improve the maintainability of dependency management in build.sbt by extracting all dependency versions into variables. This is a common best practice in sbt projects and would make future updates easier to manage.

[gemini-code-assist]

For better maintainability and to avoid magic strings, it's a good practice to extract dependency versions into vals. This is already being done for Scala versions in this file. Applying this to library dependencies would improve consistency and make version management easier.

For example, you could define versions near the top of the file:

val airspecVersion = "2025.1.24"
val commonsCompressVersion = "1.27.1"
val xzVersion = "1.11"

And then use them in libraryDependencies:

libraryDependencies ++= Seq(
  "org.wvlet.airframe" %% "airspec"          % airspecVersion % Test,
  "org.apache.commons"  % "commons-compress" % commonsCompressVersion,
  "org.tukaani"         % "xz"               % xzVersion
)

[xerial-bot]

Superseded by #614.