Update gopkg.in/yaml.v3 to v3.0.0 #2876
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
AkihiroSuda
approved these changes
May 24, 2022
|
Check the CI results |
SaschaSchwarze0
force-pushed
the
sascha-update-yaml-v3
branch
from
4ea58f1 to
22c8206
Compare
Interesting, wondering how I managed to get it updated in vendor, but the modules.txt not updated. Ran |
Signed-off-by: Sascha Schwarze <schwarzs@de.ibm.com>
SaschaSchwarze0
force-pushed
the
sascha-update-yaml-v3
branch
from
22c8206 to
df16694
Compare
crazy-max
approved these changes
May 30, 2022
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.
Based on
go tool nm, the buildkitd and buildctl binary are not affected by CVE-2022-28948, but not every security scanning tool is smart enough to detect that.