iot/base-images
0
0
Fork 0
mirror of https://gitlab.com/fedora/bootc/base-images.git synced 2026-09-02 14:30:46 +00:00
Code Issues Projects Releases Packages Wiki Activity

docs: update RELEASE.md steps for new Fedora version

Browse source 
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.
This commit is contained in:
Dusty Mabe 2026-08-24 16:37:40 -04:00
commit 6d9956d3f7
No known key found for this signature in database
GPG key ID: D0181D71212F1FA4
1 changed files with 4 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

7
RELEASE.md
View file

@ -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: