Closed
Conversation
|
This is already the third PR trying to address the above mentioned security vulnerability. Could anyone from stretchr please review any one of those PRs and get it merged? Thanks. |
|
#1192 already includes the bump to v3.0.1 let's focus on getting that merged in favor of this merge request. |
Collaborator
|
Closing as this has already been addressed |
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
5 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.
Summary
Fixing CVE-2022-28948
Changes
Updates gopkg.in/yaml.v3 to v3.0.0
Motivation
Security fix
Related issues
go-yaml/yaml#666