From 6d9956d3f7ad7d1d524d9c2a009f2bbc4d88f336 Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Mon, 24 Aug 2026 16:37:40 -0400 Subject: [PATCH] docs: update RELEASE.md steps for new Fedora version The tenant definitions are in a different place now and also there are many more .yaml files so use `find` to find all the files to then run `sed` on. Also combine step 4 and step 5 together since they are both touching the tenants-config and the change should go into the same MR. --- RELEASE.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index e11ca1c..fe2f647 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -234,18 +234,17 @@ Add package rules for the new version in `renovate.json`. See the existing rules **Repository:** https://gitlab.com/fedora/infrastructure/konflux/tenants-config ```bash -cd cluster/kfluxfedorap01/bootc-tenant/applications/fedora-bootc/ +cd clusters/kflux-fedora-01/tenants/bootc-tenant/applications/fedora-bootc/ NEW_RELEASE=44 # Copy from rawhide cp -r rawhide $NEW_RELEASE # Update version references -sed -i "s/rawhide/$NEW_RELEASE/g" $NEW_RELEASE/**/*.yaml sed -i "s/compose-rawhide-id/compose-branched-id/" $NEW_RELEASE/releaseplans/release-to-quay-io/kustomization.yaml +find "${NEW_RELEASE}/" -type f | xargs sed -i "s/rawhide/$NEW_RELEASE/g" ``` -#### Step 5: Register the New Version (tenants-config repo) Add the new version to `fedora-bootc/kustomization.yaml`: @@ -259,6 +258,8 @@ resources: - "42" ``` +See [MR !237](https://gitlab.com/fedora/infrastructure/konflux/tenants-config/-/merge_requests/237) for reference (F45 addition). + ### Removing an EOL Fedora Version from Konflux When a Fedora version reaches EOL (e.g., F42), follow these steps: