Skip to content
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

[1.20][go1.15] Update to go1.15.8 #98962

Conversation

cpanato
Copy link
Member

@cpanato cpanato commented Feb 10, 2021

What type of PR is this?

/kind feature
/area dependency

What this PR does / why we need it:

  • Update to go1.15.8

Tracking issue: kubernetes/release#1895
Slack thread: https://kubernetes.slack.com/archives/CJH2GBF7Y/p1612545791171200

/assign @justaugustus
cc: @kubernetes/release-engineering

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

- Kubernetes is now built using go1.15.8

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


@k8s-ci-robot k8s-ci-robot added this to the v1.20 milestone Feb 10, 2021
@k8s-ci-robot k8s-ci-robot added do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/feature Categorizes issue or PR as related to a new feature. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. area/dependency Issues or PRs related to dependency changes cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Feb 10, 2021
@cpanato cpanato changed the title [1.19][go1.15] Update to go1.15.8 [1.20][go1.15] Update to go1.15.8 Feb 10, 2021
@cpanato
Copy link
Member Author

cpanato commented Feb 10, 2021

/priority important-soon

@k8s-ci-robot k8s-ci-robot added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. area/provider/gcp Issues or PRs related to gcp provider area/release-eng Issues or PRs related to the Release Engineering subproject area/test sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. and removed needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Feb 10, 2021
@k8s-ci-robot k8s-ci-robot added sig/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Feb 10, 2021
@cpanato
Copy link
Member Author

cpanato commented Feb 10, 2021

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Feb 10, 2021
@dims
Copy link
Member

dims commented Feb 10, 2021

/retest
/approve

@cpanato cpanato changed the title [1.20][go1.15] Update to go1.15.8 WIP [1.20][go1.15] Update to go1.15.8 Feb 10, 2021
@k8s-ci-robot k8s-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 10, 2021
@cpanato cpanato force-pushed the automated-cherry-pick-of-#98834-upstream-release-1.20 branch from 1c9ab82 to c42c05c Compare February 15, 2021 15:07
@cpanato
Copy link
Member Author

cpanato commented Feb 15, 2021

/test pull-kubernetes-e2e-kind

@cpanato cpanato force-pushed the automated-cherry-pick-of-#98834-upstream-release-1.20 branch from c42c05c to 30b3b21 Compare February 15, 2021 19:09
@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Feb 15, 2021
@cpanato cpanato force-pushed the automated-cherry-pick-of-#98834-upstream-release-1.20 branch from 30b3b21 to 0e83611 Compare February 15, 2021 19:12
@cpanato
Copy link
Member Author

cpanato commented Feb 15, 2021

/test pull-kubernetes-node-e2e

@cpanato cpanato force-pushed the automated-cherry-pick-of-#98834-upstream-release-1.20 branch from 0e83611 to 58c5493 Compare February 16, 2021 08:09
@justaugustus justaugustus added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Feb 16, 2021
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. label Feb 16, 2021
@justaugustus
Copy link
Member

/lgtm
/approve
/priority critical-urgent
/assign @liggitt

@k8s-ci-robot k8s-ci-robot added priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. lgtm "Looks good to me", indicates that a PR is ready to be merged. labels Feb 16, 2021
@justaugustus
Copy link
Member

/assign @mkumatag

@mkumatag
Copy link
Member

/lgtm
/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cpanato, dims, justaugustus, mkumatag

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 16, 2021
@k8s-ci-robot k8s-ci-robot merged commit e4f2398 into kubernetes:release-1.20 Feb 16, 2021
@cpanato cpanato deleted the automated-cherry-pick-of-#98834-upstream-release-1.20 branch February 16, 2021 11:17
@liggitt
Copy link
Member

liggitt commented Feb 16, 2021

lgtm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/dependency Issues or PRs related to dependency changes area/provider/gcp Issues or PRs related to gcp provider area/release-eng Issues or PRs related to the Release Engineering subproject area/test cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants