[19.03 backport] vendor: Bump gopkg.in/yaml.v2#2119
Merged
andrewhsu merged 1 commit intodocker:19.03from Oct 3, 2019
Merged
Conversation
Signed-off-by: Christopher Crone <christopher.crone@docker.com> (cherry picked from commit 91cf8b0) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Member
Author
|
ping @silvin-lubecki @chris-crone @vdemeester PTAL |
Contributor
|
Do we need this for 19.03.3? |
thaJeztah
commented
Oct 2, 2019
| } | ||
|
|
||
| func (d *decoder) unmarshal(n *node, out reflect.Value) (good bool) { | ||
| d.decodeCount++ |
Member
Author
There was a problem hiding this comment.
@kolyshkin not critical, but it probably won't hurt to have; the beef of the change is in this file (although their fix is a bit weird)
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
6 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.
backport of #2117
To mitigate against malicious YAML (kubernetes/kubernetes#83253), we had implemented our own patch to the yams.v2 library. Now that there's an upstream fix, this PR brings us back to using the upstream library.
Description for the changelog