Skip to content

Commit 04e68e1

Browse files
michi-covalentnathanjsweet
authored andcommitted
patch: Remove the step to bump base / runtime images
Now Renovate takes care of bumping base / runtime images. I boldly assert that release managers should not be responsible for updating dependencies anyways. Signed-off-by: Michi Mutsuzaki <[email protected]>
1 parent c62adf8 commit 04e68e1

File tree

1 file changed

+0
-7
lines changed

1 file changed

+0
-7
lines changed

.github/ISSUE_TEMPLATE/release_template_patch.md

-7
Original file line numberDiff line numberDiff line change
@@ -31,13 +31,6 @@ assignees: ''
3131
- [ ] Check that there are no [release blockers] for the targeted release version.
3232
- [ ] Ensure that outstanding [backport PRs] are merged (these may be skipped on
3333
case by case basis in coordination with the backporter).
34-
- [ ] Check whether the base images for the target stable branch need to be rebuilt.
35-
See [quay.io/cilium/cilium-ci](https://quay.io/repository/cilium/cilium-ci?tab=tags)
36-
and use the search box to filter for `v` to match branch versions.
37-
If the target branch has CVEs listed as "fixable" under the "Security Scan"
38-
column, then you need to update the runtime images.
39-
If rebuild is required (for example due to CVEs reported in current images), follow
40-
[this guide](https://docs.cilium.io/en/latest/contributing/development/images/#update-cilium-builder-and-cilium-runtime-images).
4134
- [ ] Check with @cilium/security team if there are any security fixes to include
4235
in the release.
4336
- [ ] Execute `release projects sync --repo cilium/cilium --current-version X.Y.Z --next-dev-version X.Y.W` to

0 commit comments

Comments
 (0)