Update golang.org/x/text for CVE-2022-32149 #5007
Closed
Conversation
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
wgliang
force-pushed
the
bugfix/cve-2022-32149
branch
4 times, most recently
from
6de5719 to
608e86c
Compare
|
https://github.com/cortexproject/cortex/actions/runs/3583814836/jobs/6033812268 The local lint check did not see any exceptions. Is there something wrong with the robot? |
|
Can u try to run |
wgliang
force-pushed
the
bugfix/cve-2022-32149
branch
from
608e86c to
44c0ddb
Compare
Signed-off-by: wangguoliang <iamwgliang@gmail.com>
wgliang
force-pushed
the
bugfix/cve-2022-32149
branch
from
44c0ddb to
3c7face
Compare
|
#5008 already contains this fix, I will close this PR. |
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 this PR does:
Updates golang.org/x/text for GHSA-69ch-w2m2-3vjp (see here for more information).
Which issue(s) this PR fixes:
Fixes #
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]