[FLINK-37968] Bump Netty version to v4.1.122.Final#218
Closed
somaniraghav wants to merge 1 commit intoapache:mainfrom
Closed
[FLINK-37968] Bump Netty version to v4.1.122.Final#218somaniraghav wants to merge 1 commit intoapache:mainfrom
somaniraghav wants to merge 1 commit intoapache:mainfrom
Conversation
| Thanks for opening this pull request! Please check out our contributing guidelines. (https://flink.apache.org/contributing/how-to-contribute.html) |
somaniraghav changed the title 
1 similar comment
| @AHeise @leekeiabstraction @hlteoh37 @darenwkt can you review this PR? |
Contributor
| Superseded by #221 |
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 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.
Purpose of the change
Bump Netty version to v4.1.122.Final
Verifying this change
This change is already covered by existing tests.
Significant changes
(Please check any boxes [x] if the answer is "yes". You can first publish the PR and check them afterwards, for convenience.)
@Public(Evolving))