-
Notifications
You must be signed in to change notification settings - Fork 505
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update/build Golang 1.17rc1 and 1.16.6 images #2168
Conversation
Signed-off-by: Stephen Augustus <[email protected]>
Signed-off-by: Stephen Augustus <[email protected]>
This commit modifies the k8s-ci-builder files and the dependencies.yaml manifest to golang 1.16.6. Signed-off-by: Adolfo García Veytia (Puerco) <[email protected]> Co-authored-by: Stephen Augustus <[email protected]>
Signed-off-by: Stephen Augustus <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/hold for more eyes if needed
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cpanato, justaugustus, saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
1 similar comment
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cpanato, justaugustus, saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold cancel |
/kind feature
/area dependency release-eng/security
What this PR does / why we need it:
Tracking issue: #2157
Supersedes #2166 to fix a verify failure created by the "next candidate" (go1.17rc1) images.
/assign @puerco @saschagrunert @cpanato @xmudrii
cc: @kubernetes/release-engineering
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?