-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
🌱 fix: run make generate to fix ci #4353
🌱 fix: run make generate to fix ci #4353
Conversation
Hi @monteiro-renato. 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 Once the patch is verified, the new status will be reflected by the 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-sigs/prow repository. |
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.
What we need to is un PR that ":sparkles: Upgrade cert-manager from to "
This PR must to have all required changes to move within we cannot change the samples in a PR and the value used in another
This PR will close: #4355 (which is used to let us know aware of the new version )
Closing this one in order of we move like: #4353 (review) Feel free to re-open if you think that is needed. |
/ok-to-test |
The bump should not get merged |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: camilamacedo86, monteiro-renato 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 |
45925f3
into
kubernetes-sigs:master
There was a release about 2 hours ago
https://github.com/cert-manager/cert-manager/releases/tag/v1.16.2
I guess this issue will eventually occur again if nothing is done to prevent it.