Update gopkg.in/yaml.v3 to v3.0.1#308
Closed
SaschaSchwarze0 wants to merge 1 commit into
Closed
Conversation
SaschaSchwarze0
force-pushed
the
sascha-update-yaml.v3
branch
from
3d9fb02 to
8bf889d
Compare
Member
|
I think this should be fixed in the testify repo |
Signed-off-by: Sascha Schwarze <schwarzs@de.ibm.com>
SaschaSchwarze0
force-pushed
the
sascha-update-yaml.v3
branch
from
8bf889d to
4ef2c37
Compare
SaschaSchwarze0
changed the title
Author
Yeah, ideally. But that's a repo with >100 pull requests where things get rarely merged, at least three of the open PRs aim to fix it (stretchr/testify#1190, stretchr/testify#1192, stretchr/testify#1193). I leave it up to you. In the meantime, I updated the PR to go to v3.0.1 based on go-yaml/yaml#666 (comment). |
Member
|
Thanks, but let me just remove testify |
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
2 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.
Based on
go tool nm, the rootlesskit binary is not affected by CVE-2022-28948, but not every security scanning tool is smart enough to detect that.