Update airspec to 2025.1.26

[xerial-bot]

About this PR

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

📜 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 automates the update of the airspec test library to its latest patch version. This ensures the project benefits from the most recent bug fixes and minor improvements in the testing framework, maintaining compatibility and stability without introducing breaking changes.

Highlights

• Dependency Update: The org.wvlet.airframe:airspec test library has been updated from version 2025.1.22 to 2025.1.26.
• Patch Version: This update is a patch version increment, indicating minor bug fixes and improvements without breaking changes.

🧠 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 from Scala Steward updates the airspec test library to version 2025.1.26. The change is a straightforward dependency bump. I have one suggestion for improving the maintainability of the build.sbt file, but it is not a blocker for this update.

[gemini-code-assist]

For better maintainability, it's a good practice to extract dependency versions into val definitions. This centralizes version management, making updates easier and the build file cleaner. For example, you could define val airspecVersion = "2025.1.26" at the top of the file and reference it here. This is a suggestion for future improvement and does not need to block this automated PR.

[xerial-bot]

Superseded by #615.