Update airframe-http, airframe-http-netty, ... to 2025.1.27

[xerial-bot]

About this PR

📦 Updates

• org.wvlet.airframe:airframe-http
• org.wvlet.airframe:airframe-http-netty
• org.wvlet.airframe:airframe-launcher
• org.wvlet.airframe:airframe-rx-html
• org.wvlet.airframe:sbt-airframe

from 2025.1.26 to 2025.1.27

📜 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" } ]

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

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

^{labels: library-update}

[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 systematically updates the org.wvlet.airframe suite of libraries across various example projects to their latest patch version, 2025.1.27. The primary purpose is to ensure that the project's dependencies remain current, incorporating any bug fixes, minor improvements, or security patches introduced in the new airframe release. This update helps maintain the stability and compatibility of the example applications with the most recent airframe ecosystem.

Highlights

• Dependency Updates: The pull request updates multiple org.wvlet.airframe dependencies, including airframe-http, airframe-http-netty, airframe-launcher, airframe-rx-html, and sbt-airframe, from version 2025.1.26 to 2025.1.27.
• Automated Process: This update is an automated process managed by Scala Steward, ensuring the project's dependencies remain current with the latest patch releases.

🧠 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 airframe dependency to version 2025.1.27 across several example projects. The changes are straightforward version bumps. I've added one suggestion to centralize the version definition for these example projects to improve maintainability for future updates.

[gemini-code-assist]

To improve maintainability and avoid inconsistencies, I suggest centralizing the AIRFRAME_VERSION. This version string is duplicated in several example build.sbt files, and also in project/plugins.sbt files.

A common practice in sbt projects is to define versions in a single place. For example, you could create a project/Versions.scala file:

object Versions {
  val airframe = "2025.1.27"
}

Then, you can reference this value in your build files:

• In build.sbt: val AIRFRAME_VERSION = Versions.airframe
• In project/plugins.sbt: addSbtPlugin("org.wvlet.airframe" % "sbt-airframe" % Versions.airframe)

This change would make future dependency updates much easier to manage by only requiring a change in one file.