-
Notifications
You must be signed in to change notification settings - Fork 504
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
Build k8s-ci-builder and k8s-cloud-bulider with Go 1.22.0 and 1.21.7 #3463
Merged
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
k8s-ci-robot
added
the
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
label
Feb 10, 2024
k8s-ci-robot
added
the
kind/feature
Categorizes issue or PR as related to a new feature.
label
Feb 10, 2024
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cpanato 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 |
k8s-ci-robot
added
the
area/release-eng
Issues or PRs related to the Release Engineering subproject
label
Feb 10, 2024
k8s-ci-robot
added
cncf-cla: yes
Indicates the PR's author has signed the CNCF CLA.
sig/release
Categorizes an issue or PR as relevant to SIG Release.
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
needs-priority
size/S
Denotes a PR that changes 10-29 lines, ignoring generated files.
labels
Feb 10, 2024
45 tasks
k8s-ci-robot
added
size/M
Denotes a PR that changes 30-99 lines, ignoring generated files.
and removed
size/S
Denotes a PR that changes 10-29 lines, ignoring generated files.
labels
Feb 10, 2024
cpanato
changed the title
Build k8s-ci-builder and k8s-cloud-bulider with Go 1.22.0
Build k8s-ci-builder and k8s-cloud-bulider with Go 1.22.0 and 1.21.7
Feb 10, 2024
Signed-off-by: cpanato <[email protected]>
/lgtm |
k8s-ci-robot
added
the
lgtm
"Looks good to me", indicates that a PR is ready to be merged.
label
Feb 10, 2024
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/release-eng
Issues or PRs related to the Release Engineering subproject
cncf-cla: yes
Indicates the PR's author has signed the CNCF CLA.
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.
needs-priority
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
sig/release
Categorizes an issue or PR as relevant to SIG Release.
size/M
Denotes a PR that changes 30-99 lines, ignoring generated files.
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 type of PR is this?
/kind feature
What this PR does / why we need it:
/assign @xmudrii @ameukam @Verolop
cc @dims @kubernetes/release-engineering
Which issue(s) this PR fixes:
xref #3280
Does this PR introduce a user-facing change?