🌱 Fix GO-2020-0020 #1047
Merged
🌱 Fix GO-2020-0020 #1047
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
Fixes the reference to version of library that has the fix for GO-2020-0020 https://go.googlesource.com/vulndb/+/refs/heads/master/reports/GO-2020-0020.yaml
naveensrinivasan
requested review from
azeemshaikh38,
inferno-chromium and
laurentsimon
|
Integration tests success for 87bcbae0d6f825d2f502cc8475f343179cac0b1c |
|
Integration tests success for ee63332c4b31363b16c4bbe123b62ae548e31da9 |
laurentsimon
approved these changes
Sep 22, 2021
|
Integration tests success for 6153e2bafbd23d35c590a4541ca70ab62c6ccf21 |
|
Integration tests success for 99b1aa9959c415d4c1301286bc855f5450baf4dd |
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 kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Bug Fix
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Fixes the reference to version of library that has the fix for GO-2020-0020
https://go.googlesource.com/vulndb/+/refs/heads/master/reports/GO-2020-0020.yaml
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
None
None