Bump netaddr gem to 1.5.3 to fix CVE-2019-17383 #2373
Merged
Conversation
This file contains 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
Consume netaddr release from github since it hasn't been published on rubygems yet. For more context see: - dspinhirne/netaddr-rb#29 - #2369 Co-authored-by: Shilpa Chandrashekara <[email protected]>
|
@FlorianNachtigall is this PR ready for review? Asking because it is still in draft status. |
|
Tested this on one of our Dev Landscapes and it is ready to be reviewed. |
ramonskie
approved these changes
May 9, 2022
ramonskie
requested review from
a team,
jpalermo and
lnguyen
and removed request for
a team
|
Thanks! @FlorianNachtigall |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 is this change about?
As discussed in #2369 lets consume the fixed netaddr version 1.5.3 from github directly since it hasn't been published on rubygems yet.
@lnguyen @rkoster, do you mind reviewing the PR?
Please provide contextual information.
What tests have you run against this PR?
How should this change be described in bosh release notes?
Does this PR introduce a breaking change?
Tag your pair, your PM, and/or team!
@ShilpaChandrashekara
@friegger
@cloudfoundry/cf-bosh-europe