This repository has been archived by the owner on Mar 9, 2022. It is now read-only.
vendor: golang.org/x/crypto 1d94cc7ab1c630336ab82ccb9c9cda72a875c382 #1402
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
full diff: golang/crypto@60c769a...1d94cc7 Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
|
/test pull-cri-containerd-node-e2e |
mikebrow
approved these changes
Feb 19, 2020
|
did you want to just add a commit to this PR tomorrow? |
|
I'm fine either way; my main reason was so that updating the security fix would be a small diff, and would (if needed) allow visual review of the diff (also to decide if it's important to backport to release branches). |
|
/lgtm |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
full diff: golang/crypto@60c769a...1d94cc7
I'm doing a around across repositories to update in preparation of a security release that was announced for tomorrow (so that we can update again with just the changes related to that fix);
https://groups.google.com/d/msgid/golang-announce/CA%2B2K_Kox3xkjj6gWkp%3DY6fmp7sO4T%2BbgudjjZZ%3Duwgp476pmEw%40mail.gmail.com