-
Notifications
You must be signed in to change notification settings - Fork 828
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
Image promotion for build-image v1.25.0-go1.19-bullseye.0 / v2.3.1-go1.19-bullseye.0 #4047
Image promotion for build-image v1.25.0-go1.19-bullseye.0 / v2.3.1-go1.19-bullseye.0 #4047
Conversation
…1.19-bullseye.0 Signed-off-by: Adolfo García Veytia (Puerco) <adolfo.garcia@uservers.net>
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims, puerco 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 |
For some reason, we have a big diff reordering the last PR to the manifests. I've checked and beyond moving things, the diff is only adding new digests which are related to the tags being promoted:
This means the promo PR is OK. After the manifest sorting was merged, this should not happen but once. @kubernetes/release-managers let's make sure everybody is using the latest kpromo version. |
/hold cancel |
Image promotion for build-image v1.25.0-go1.19-bullseye.0 / v2.3.1-go1.19-bullseye.0
This is an automated PR generated from
kpromo
/hold
cc: @kubernetes/release-engineering