Skip to content

fix: update dependency io.netty:netty-transport-native-epoll to v4.2.13.final #804

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
renovate-bot wants to merge 1 commit into
base: main
Choose a base branch
from
+1 −1
Open

fix: update dependency io.netty:netty-transport-native-epoll to v4.2.13.final #804

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion spannerlib/wrappers/spannerlib-java/pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@
<dependency>
<groupId>io.netty</groupId>
<artifactId>netty-transport-native-epoll</artifactId>
<version>4.2.12.Final</version>
<version>4.2.13.Final</version>
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot May 6, 2026

Choose a reason for hiding this comment

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

medium

Hardcoding the version for netty-transport-native-epoll can lead to version mismatches with other Netty artifacts managed by the imported BOMs (such as grpc-bom on line 40 or google-cloud-spanner-bom on line 25). It is generally recommended to remove the explicit version and let the BOM manage it, or use a netty-bom in the dependencyManagement section to ensure all Netty modules are kept in sync. This prevents potential runtime linkage errors like NoSuchMethodError. If you must update dependencies manually outside of a BOM, verify the version's release date to ensure it is current and compatible with other libraries.

References
  1. When updating dependencies, especially those not managed by a BOM, verify the version's release date to ensure it is current and compatible with other libraries.

</dependency>
<!-- Dependencies for using C library -->
<dependency>
Expand Down
Loading