Skip to content

Update go version to 1.20.9 #1412

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

Merged
merged 1 commit into from
Oct 16, 2023

Conversation

dannawang0221
Copy link
Contributor

@dannawang0221 dannawang0221 commented Oct 13, 2023

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind bug

What this PR does / why we need it:
Fix for CVE-2023-39323
Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

CVE fixes: CVE-2023-39323

@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/bug Categorizes issue or PR as related to a bug. labels Oct 13, 2023
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Oct 13, 2023
@k8s-ci-robot
Copy link
Contributor

Hi @dannawang0221. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Oct 13, 2023
@dannawang0221
Copy link
Contributor Author

/assign @msau42

@pwschuurman
Copy link
Contributor

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Oct 13, 2023
@pwschuurman
Copy link
Contributor

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added lgtm "Looks good to me", indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Oct 13, 2023
@pwschuurman
Copy link
Contributor

Integration test failures will be fixed in #1413

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 16, 2023
@dannawang0221
Copy link
Contributor Author

/assign @tyuchn

@tyuchn
Copy link
Contributor

tyuchn commented Oct 16, 2023

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 16, 2023
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dannawang0221, pwschuurman, tyuchn

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 merged commit 699ad83 into kubernetes-sigs:master Oct 16, 2023
@tyuchn
Copy link
Contributor

tyuchn commented Oct 16, 2023

/cherry-pick release-1.12

@tyuchn
Copy link
Contributor

tyuchn commented Oct 16, 2023

/cherry-pick release-1.11

@tyuchn
Copy link
Contributor

tyuchn commented Oct 16, 2023

/cherry-pick release-1.10

@k8s-infra-cherrypick-robot

@tyuchn: new pull request created: #1416

In response to this:

/cherry-pick release-1.12

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-infra-cherrypick-robot

@tyuchn: new pull request created: #1417

In response to this:

/cherry-pick release-1.11

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-infra-cherrypick-robot

@tyuchn: new pull request created: #1418

In response to this:

/cherry-pick release-1.10

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@tyuchn
Copy link
Contributor

tyuchn commented Oct 16, 2023

/cherry-pick release-1.9

@k8s-infra-cherrypick-robot

@tyuchn: new pull request created: #1419

In response to this:

/cherry-pick release-1.9

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@tyuchn
Copy link
Contributor

tyuchn commented Oct 16, 2023

/cherry-pick release-1.9

@tyuchn
Copy link
Contributor

tyuchn commented Oct 16, 2023

/cherry-pick release-1.10

@tyuchn
Copy link
Contributor

tyuchn commented Oct 16, 2023

/cherry-pick release-1.11

@tyuchn
Copy link
Contributor

tyuchn commented Oct 16, 2023

/cherry-pick release-1.12

@k8s-infra-cherrypick-robot

@tyuchn: new pull request created: #1428

In response to this:

/cherry-pick release-1.9

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-infra-cherrypick-robot

@tyuchn: new pull request created: #1429

In response to this:

/cherry-pick release-1.10

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-infra-cherrypick-robot

@tyuchn: new pull request created: #1430

In response to this:

/cherry-pick release-1.11

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-infra-cherrypick-robot

@tyuchn: new pull request created: #1431

In response to this:

/cherry-pick release-1.12

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@tyuchn
Copy link
Contributor

tyuchn commented Oct 18, 2023

/cherry-pick release-1.7

@tyuchn
Copy link
Contributor

tyuchn commented Oct 18, 2023

/cherry-pick release-1.8

@k8s-infra-cherrypick-robot

@tyuchn: #1412 failed to apply on top of branch "release-1.7":

Applying: Update go version to 1.20.9
Using index info to reconstruct a base tree...
M	Dockerfile.Windows
M	Dockerfile.debug
Falling back to patching base and 3-way merge...
Auto-merging Dockerfile.debug
CONFLICT (content): Merge conflict in Dockerfile.debug
Auto-merging Dockerfile.Windows
CONFLICT (content): Merge conflict in Dockerfile.Windows
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Update go version to 1.20.9
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-1.7

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-infra-cherrypick-robot

@tyuchn: #1412 failed to apply on top of branch "release-1.8":

Applying: Update go version to 1.20.9
Using index info to reconstruct a base tree...
M	Dockerfile.Windows
M	Dockerfile.debug
Falling back to patching base and 3-way merge...
Auto-merging Dockerfile.debug
CONFLICT (content): Merge conflict in Dockerfile.debug
Auto-merging Dockerfile.Windows
CONFLICT (content): Merge conflict in Dockerfile.Windows
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Update go version to 1.20.9
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-1.8

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

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. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/bug Categorizes issue or PR as related to a bug. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants