ci(flatpak): disable release-tag trigger while the build is blocked #315
No reviewers
Labels
No labels
area:auth
area:ci
area:db
area:infra
area:native
area:pwa
area:service
epic
feature
foundation
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
james/carol!315
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "313-disable-flatpak-build"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The Flatpak release job fails on every
v*.*.*tag atflatpak-builder'sbwrapuser-namespace step in the unprivileged runner container (#313). The fix needs--privilegedplus 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*.*.*"]toworkflow_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, Androidrelease-android.yml) are unaffected.Refs #313 (does not close — the underlying build blocker remains).
🤖 Generated with Claude Code
📊 Test coverage
Patch coverage: no testable lines changed.
Overall (
app/,lib/,db/, excluding UI per ADR-0019):Soft thresholds per ADR-0019. Coverage is informational and does not block merge.