Prepare release assets for multi-arch GitHub releases

Author: Sopwit

.github/workflows/release.yml

@@ -191,11 +191,41 @@ jobs:
             sha256sum * > "ro-control-${VERSION}-${RPM_ARCH}-SHA256SUMS.txt"
           )
 
+      - name: Create per-arch release bundle
+        env:
+          VERSION: ${{ needs.metadata.outputs.version }}
+          RPM_ARCH: ${{ matrix.arch }}
+        run: |
+          mkdir -p dist/release
+
+          RPM_FILE="$(find dist/rpm -maxdepth 1 -type f -name "*.${RPM_ARCH}.rpm" | head -n1)"
+          INFO_FILE="dist/rpm/ro-control-${VERSION}-${RPM_ARCH}-info.txt"
+          REQUIRES_FILE="dist/rpm/ro-control-${VERSION}-${RPM_ARCH}-requires.txt"
+          CHECKSUM_FILE="dist/rpm/ro-control-${VERSION}-${RPM_ARCH}-SHA256SUMS.txt"
+          BUNDLE_DIR="dist/release/ro-control-${VERSION}-${RPM_ARCH}"
+          BUNDLE_NAME="ro-control-${VERSION}-${RPM_ARCH}-fedora42.tar.gz"
+
+          if [[ -z "${RPM_FILE}" ]]; then
+            echo "Failed to locate built ${RPM_ARCH} RPM for release bundling." >&2
+            exit 1
+          fi
+
+          mkdir -p "${BUNDLE_DIR}"
+          cp "${RPM_FILE}" "${BUNDLE_DIR}/"
+          cp "${INFO_FILE}" "${BUNDLE_DIR}/"
+          cp "${REQUIRES_FILE}" "${BUNDLE_DIR}/"
+          cp "${CHECKSUM_FILE}" "${BUNDLE_DIR}/"
+
+          tar -C dist/release -czf "dist/release/${BUNDLE_NAME}" "ro-control-${VERSION}-${RPM_ARCH}"
+          rm -rf "${BUNDLE_DIR}"
+
       - name: Upload RPM artifacts
         uses: actions/upload-artifact@v4
         with:
           name: ro-control-rpm-${{ matrix.arch }}-${{ needs.metadata.outputs.version }}
-          path: dist/rpm/*
+          path: |
+            dist/rpm/*
+            dist/release/*
 
   release:
     name: Create GitHub Release
@@ -224,3 +254,4 @@ jobs:
             dist/*SHA256SUMS.txt
             dist/*-requires.txt
             dist/*-info.txt
+            dist/*-fedora42.tar.gz

README.md

@@ -114,7 +114,7 @@ Additional PNG screenshots should be added before wider store distribution.
 
 ### RPM Package
 
-Download the latest Fedora `.rpm` from [Releases](https://github.com/Project-Ro-ASD/ro-Control/releases) and choose the package that matches your machine architecture (`x86_64` or `aarch64`):
+Download the latest Fedora `.rpm` or the matching release bundle from [Releases](https://github.com/Project-Ro-ASD/ro-Control/releases), then choose the asset that matches your machine architecture (`x86_64` for 64-bit x86 systems or `aarch64` for ARM64 systems):
 
 ```bash
 sudo dnf install ./ro-control-*.rpm

README.tr.md

@@ -101,7 +101,7 @@ Daha geniş mağaza / distro dağıtımı öncesinde PNG ekran görüntüleri ek
 
 ### RPM Paketi
 
-[Releases](https://github.com/Project-Ro-ASD/ro-Control/releases) sayfasından sistem mimarinize (`x86_64` veya `aarch64`) uygun en güncel Fedora `.rpm` paketini indirin:
+[Releases](https://github.com/Project-Ro-ASD/ro-Control/releases) sayfasından sistem mimarinize uygun en güncel Fedora `.rpm` paketini veya release bundle dosyasını indirin (`x86_64` = 64-bit x86 sistemler, `aarch64` = ARM64 sistemler):
 
 ```bash
 sudo dnf install ./ro-control-*.rpm

docs/RELEASE.md

@@ -36,7 +36,7 @@ Use this checklist for every production release.
 
 - [ ] Create annotated tag: `vX.Y.Z`.
 - [ ] Push tag to trigger release workflow.
-- [ ] Verify GitHub Release includes source archives, one `x86_64` RPM, one `aarch64` RPM, and one source RPM.
+- [ ] Verify GitHub Release includes source archives, one `x86_64` RPM, one `aarch64` RPM, per-arch release bundles, and one source RPM.
 - [ ] Verify the attached checksum and RPM metadata files are present.
 
 ## 6. Post-release

packaging/rpm/README.md

@@ -60,8 +60,12 @@ The GitHub release workflow builds:
 - source archives (`.tar.gz`, `.zip`)
 - one Fedora binary RPM for `x86_64`
 - one Fedora binary RPM for `aarch64`
+- one Fedora release bundle for `x86_64`
+- one Fedora release bundle for `aarch64`
 - one source RPM
 
 Each architecture job also performs a smoke install with `dnf install` and
 verifies that `ro-control --version` matches the tagged release version before
-publishing assets.
+publishing assets. Each release bundle contains the architecture-specific RPM,
+package metadata, dependency list, and checksum manifest for easier download
+from the GitHub Releases page.