Bump netty to 4.2.15.Final#5
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Similar to #2 and #4, we're updating
nettyto solve CVE related issues.I've manually tested the change with the locally built wheel, and I'm able to poll Kinesis records from LocalStack, also verified that the artifact was built with Netty 4.2.15.Final.
We should think of automating this with Dependabot + test scripts to do some small smoke tests against LocalStack to verify the library builds properly, and is able to be used.
We could re-use the sample tests here which is supposed to run against AWS, to run against LS