Skip to content

Update netty-all to 4.2.4.Final#4010

Merged
xerial merged 1 commit intomainfrom
update/netty-all-4.2.4.Final
Aug 25, 2025
Merged

Update netty-all to 4.2.4.Final#4010
xerial merged 1 commit intomainfrom
update/netty-all-4.2.4.Final

Conversation

@xerial-bot
Copy link
Copy Markdown
Collaborator

About this PR

📦 Updates io.netty:netty-all from 4.2.3.Final to 4.2.4.Final

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 = "io.netty", artifactId = "netty-all" } ]

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

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "io.netty", artifactId = "netty-all" }
}]
labels: library-update

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @xerial-bot, I'm Gemini Code Assist1! 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 performs a routine update of the netty-all dependency. The change involves bumping the version of this networking library from 4.2.3.Final to 4.2.4.Final. This is an automated update, likely aimed at incorporating the latest bug fixes or minor improvements from the Netty project.

Highlights

  • Dependency Update: Updates the io.netty:netty-all library to version 4.2.4.Final from 4.2.3.Final.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the io.netty:netty-all dependency to version 4.2.4.Final. This is a patch version bump and appears to be a routine, safe update.

While the change itself is straightforward, I've added a couple of suggestions on the build.sbt file to improve long-term maintainability:

  • Extracting the hardcoded version string into a val for consistency and easier management.
  • Considering the use of specific Netty modules instead of the netty-all artifact to create a more lean and optimized dependency graph.

These are non-blocking suggestions for future improvements.

Comment thread build.sbt
description := "Airframe HTTP Netty backend",
libraryDependencies ++= Seq(
"io.netty" % "netty-all" % "4.2.3.Final"
"io.netty" % "netty-all" % "4.2.4.Final"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For better maintainability and consistency with other dependencies in this file (e.g., GRPC_VERSION, FINAGLE_VERSION), consider extracting the Netty version to a val at the top of the build.sbt file.

For example:

val NETTY_VERSION = "4.2.4.Final"

And then use it here:

"io.netty" % "netty-all" % NETTY_VERSION

This would make future updates easier to manage.

Comment thread build.sbt
description := "Airframe HTTP Netty backend",
libraryDependencies ++= Seq(
"io.netty" % "netty-all" % "4.2.3.Final"
"io.netty" % "netty-all" % "4.2.4.Final"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The netty-all dependency includes all Netty modules, which can lead to a larger artifact size and potential dependency conflicts. It's a good practice to depend only on the specific Netty modules that your project needs.

While this is a larger change outside the scope of this version bump, you might want to consider analyzing the exact dependencies of the airframe-http-netty module and replacing netty-all with more specific artifacts like netty-codec-http, netty-handler, etc., in the future. This can help create a more lean dependency graph and avoid pulling in unnecessary transitive dependencies.

@xerial xerial merged commit bd9e1af into main Aug 25, 2025
25 checks passed
@xerial xerial deleted the update/netty-all-4.2.4.Final branch August 25, 2025 18:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants