[CELEBORN-2258] Bump Netty version from 4.1.118.Final to 4.2.10.Final #3596
+930
−656
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SteNicholas
force-pushed
the
CELEBORN-2258
branch
2 times, most recently
from
9f2fd3e to
6d4779d
Compare
SteNicholas
changed the title
SteNicholas
force-pushed
the
CELEBORN-2258
branch
from
6d4779d to
73254ef
Compare
eolivelli
reviewed
Feb 11, 2026
common/src/test/java/org/apache/celeborn/common/network/TransportClientFactorySuiteJ.java
Show resolved
Hide resolved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Bump Netty version from 4.1.118.Final to 4.2.10.Final, which follows the official community migration guide: Netty-4.2-Migration-Guide.
Why are the changes needed?
The Netty 4.2.10.Final version has been released, which netty version is 4.1.118.Final at present.
Backport:
4.2.9.Finalspark#53499Does this PR resolve a correctness bug?
No.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
CI.