Build the Flatpak on pull requests and main, and publish releases from tags #4

Merged

GrumpyStraw merged 2 commits from ci/flatpak-releases into main

2026-10-11 10:52:39 +02:00

GrumpyStraw commented

2026-10-11 10:41:40 +02:00

Owner

Build on pull requests and main

.forgejo/workflows/build.yml runs the unit tests and builds the Flatpak bundle on every pull request and every push to main. The bundle is kept as a workflow artifact for 30 days, named like strawly-music-0.1.0-ac67e06-x86_64.flatpak.

Runs on the Strawly-Music runner on TrueNAS (label flatpak), in ghcr.io/flathub-infra/flatpak-github-actions:kde-6.11, which has flatpak-builder and the KDE 6.11 SDK preinstalled.
The manifest builds with -DBUILD_TESTING=OFF, so the tests are built and run separately with flatpak run in org.kde.Sdk//6.11.
The runner's job containers are privileged, because flatpak-builder needs user namespaces for bubblewrap. The repository is public, so pull requests from forks do not run. Push a fork's branch here to build it.
Branch protection on main requires the build / build (pull_request) check to pass before merging.

Releases from tags

Pushing a tag like v0.2.0 runs the same build, then creates a Forgejo release with the .flatpak attached (actions/forgejo-release, using the automatic job token).

The build fails unless the tag matches project(strawly-music VERSION ...) in CMakeLists.txt and data/app.strawly.music.metainfo.xml has a matching <release> entry.
A tag with a dash, such as v0.2.0-rc.1, is published as a pre-release.
The bundle carries Flathub as its runtime source, so flatpak install --user strawly-music-0.2.0-x86_64.flatpak also installs org.kde.Platform//6.11.

Checked locally

The test step and the bundle step pass on this machine with the same commands: both tests pass in the SDK, and the bundle builds with the binary inside. This pull request is the first run on the runner.

## Build on pull requests and main `.forgejo/workflows/build.yml` runs the unit tests and builds the Flatpak bundle on every pull request and every push to `main`. The bundle is kept as a workflow artifact for 30 days, named like `strawly-music-0.1.0-ac67e06-x86_64.flatpak`. - Runs on the Strawly-Music runner on TrueNAS (label `flatpak`), in `ghcr.io/flathub-infra/flatpak-github-actions:kde-6.11`, which has `flatpak-builder` and the KDE 6.11 SDK preinstalled. - The manifest builds with `-DBUILD_TESTING=OFF`, so the tests are built and run separately with `flatpak run` in `org.kde.Sdk//6.11`. - The runner's job containers are privileged, because `flatpak-builder` needs user namespaces for bubblewrap. The repository is public, so pull requests from forks do not run. Push a fork's branch here to build it. - Branch protection on `main` requires the `build / build (pull_request)` check to pass before merging. ## Releases from tags Pushing a tag like `v0.2.0` runs the same build, then creates a Forgejo release with the `.flatpak` attached (`actions/forgejo-release`, using the automatic job token). - The build fails unless the tag matches `project(strawly-music VERSION ...)` in `CMakeLists.txt` and `data/app.strawly.music.metainfo.xml` has a matching `<release>` entry. - A tag with a dash, such as `v0.2.0-rc.1`, is published as a pre-release. - The bundle carries Flathub as its runtime source, so `flatpak install --user strawly-music-0.2.0-x86_64.flatpak` also installs `org.kde.Platform//6.11`. ## Checked locally The test step and the bundle step pass on this machine with the same commands: both tests pass in the SDK, and the bundle builds with the binary inside. This pull request is the first run on the runner.

GrumpyStraw added 1 commit

2026-10-11 10:41:40 +02:00

Build the Flatpak on pull requests and main, and publish releases from tags

build / build (pull_request) Failing after 6m20s

Details

build / release (pull_request) Has been skipped

Details

ac67e06f8c

GrumpyStraw added the

Kind/Feature

label

2026-10-11 10:41:46 +02:00