feat(ci): Add Fedora RPM package build workflow #961

Open

tcpipuk wants to merge 1 commit from tom/ci-fedora-rpm into main

Author	SHA1	Message	Date
Tom Foster	af53ea5599	feat(ci): Add Fedora RPM package build workflow All checks were successful Documentation / Build and Deploy Documentation (pull_request) Successful in 38s Details Release Docker Image / define-variables (pull_request) Successful in 2s Details Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m3s Details Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 5m38s Details Release Docker Image / build-image (linux/arm64, release, linux-arm64, base) (pull_request) Successful in 9m0s Details Release Docker Image / build-image (linux/amd64, release, linux-amd64, base) (pull_request) Successful in 9m9s Details Release Docker Image / merge (pull_request) Successful in 11s Details Build / Fedora RPM / build (push) Successful in 30m10s Details Build and publish RPM packages for Fedora using rpkg and official rust-packaging macros. Packages are automatically signed by Forgejo's built-in package registry (introduced in v9.0). Publishes packages to organised groups: - continuwuity (binary): base group (stable/dev/branch-name) - continuwuity-debuginfo: GROUP-debug - continuwuity (source RPM): GROUP-src Workflow triggers on pushes to relevant paths and version tags (v*). Tagged releases use clean version numbers (v1.2.3 becomes 1.2.3-1) while branch builds use sanitised branch name versioning. Uses dnf builddep to install build dependencies directly from the generated SRPM, ensuring consistency between CI and spec file without duplication. This also prevents hiding packaging issues that could occur with --nodeps fallbacks.	2025-09-06 16:52:26 +01:00