-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[release-1.2] 🌱 Update kubebuilder envtest (1.25.2 -> 1.26.0) #7864
[release-1.2] 🌱 Update kubebuilder envtest (1.25.2 -> 1.26.0) #7864
Conversation
Signed-off-by: Aniruddha Basak <[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.
Thanks for this @aniruddha2000!
For future reference you can use the cherry-pick bot to do this work automatically as here: #7717 (comment)
Some times it might not work and you'll have to open the PR manually, but it does save a good bit of the copy-past of cherry-picks 🙂
@killianmuldoon thanks for the information. From future I will try to do it with bot first |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer 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 |
/lgtm |
LGTM label has been added. Git tree hash: 501a5b42b0f92b35ce9843d38ff5e1b849e7a462
|
@aniruddha2000 Just fyi. I changed "Fixes" to "Part of". Please only use "Part of" if a PR closes a sub-task of an issue. Otherwise GitHub closes the whole issue :) |
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Part of #7671
@kubernetes-sigs/cluster-api-release-team