ci(flatpak): disable release-tag trigger while the build is blocked #315

Merged
james merged 1 commit from 313-disable-flatpak-build into main 2026-06-27 01:26:58 +00:00
Owner

The Flatpak release job fails on every v*.*.* tag at flatpak-builder's bwrap user-namespace step in the unprivileged runner container (#313). The fix needs --privileged plus act_runner/host configuration, so it's not landing immediately.

Until then, pull the Flatpak build off the release path so it stops failing on every release: switch the trigger from push: tags: ["v*.*.*"] to workflow_dispatch. The workflow stays manually runnable (so the fix in #313 can be tested) but no longer auto-runs and fails on tags. A comment documents how to restore the tag trigger.

Other release jobs (container release.yml, Android release-android.yml) are unaffected.

Refs #313 (does not close — the underlying build blocker remains).

🤖 Generated with Claude Code

The Flatpak release job fails on every `v*.*.*` tag at `flatpak-builder`'s `bwrap` user-namespace step in the unprivileged runner container (#313). The fix needs `--privileged` **plus** act_runner/host configuration, so it's not landing immediately. Until then, pull the Flatpak build off the release path so it stops failing on every release: switch the trigger from `push: tags: ["v*.*.*"]` to `workflow_dispatch`. The workflow stays **manually runnable** (so the fix in #313 can be tested) but no longer auto-runs and fails on tags. A comment documents how to restore the tag trigger. Other release jobs (container `release.yml`, Android `release-android.yml`) are unaffected. Refs #313 (does not close — the underlying build blocker remains). 🤖 Generated with [Claude Code](https://claude.com/claude-code)
ci(flatpak): disable release-tag trigger while the build is blocked
All checks were successful
Commits / Conventional Commits (pull_request) Successful in 24s
PR / Static analysis (pull_request) Successful in 1m9s
PR / OSV-Scanner (pull_request) Successful in 19s
PR / OpenAPI (pull_request) Successful in 2m58s
PR / Lint (pull_request) Successful in 3m31s
PR / Trivy (image) (pull_request) Successful in 1m46s
PR / Package age policy (soft) (pull_request) Successful in 18s
Secrets / gitleaks (pull_request) Successful in 15s
PR / pnpm audit (pull_request) Successful in 2m44s
PR / Build (pull_request) Successful in 4m16s
PR / Typecheck (pull_request) Successful in 4m49s
PR / Client (web export smoke) (pull_request) Successful in 4m3s
PR / Coverage (soft) (pull_request) Successful in 3m25s
PR / Test (postgres) (pull_request) Successful in 4m24s
PR / Test (sqlite) (pull_request) Successful in 4m29s
5430030028
The Flatpak release job fails on every v*.*.* tag at flatpak-builder's
bwrap user-namespace step in the unprivileged runner container (#313).
Until that's fixed (needs --privileged + act_runner config), pull it off
the release path: switch the trigger from `push: tags` to
`workflow_dispatch` so it no longer runs (and fails) on every release,
but stays manually runnable to test the fix.

Refs #313

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

📊 Test coverage

Patch coverage: no testable lines changed.

Overall (app/, lib/, db/, excluding UI per ADR-0019):

Metric Value Soft target
Lines 81.6% ≥ 50%
Branches 72.8% ⚠️ ≥ 75%
Functions 91.1% informational

Soft thresholds per ADR-0019. Coverage is informational and does not block merge.

<!-- coverage-comment --> ## 📊 Test coverage **Patch coverage:** no testable lines changed. **Overall** (`app/`, `lib/`, `db/`, excluding UI per ADR-0019): | Metric | Value | Soft target | |---|---|---| | Lines | 81.6% ✅ | ≥ 50% | | Branches | 72.8% ⚠️ | ≥ 75% | | Functions | 91.1% | informational | Soft thresholds per [ADR-0019](docs/adr/0019-coverage-soft-targets.md). Coverage is informational and does not block merge.
james merged commit 4b53dfdc1a into main 2026-06-27 01:26:58 +00:00
james deleted branch 313-disable-flatpak-build 2026-06-27 01:26:59 +00:00
Sign in to join this conversation.
No description provided.