matt/flotilla
1
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

Build F-Droid last in CI so a broken F-Droid build can't hold back the rest of the release

Browse source
This commit is contained in:
Jon Staab 2026-09-25 08:50:36 -07:00
parent 948707ae60
commit 46de564068
2 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -231,8 +231,8 @@ store shows the same text. The APK and zapstore share one artifact, whose path l
F-Droid builds from the tag on its own servers and ships our apk instead of its own when the two F-Droid builds from the tag on its own servers and ships our apk instead of its own when the two
match, so it keeps our signature ([reproducible builds](fdroid/README.md)). The `fdroid` step makes match, so it keeps our signature ([reproducible builds](fdroid/README.md)). The `fdroid` step makes
that apk the way F-Droid will, and if the build breaks, the workflow stops before attaching the that apk the way F-Droid will. It runs last in CI, so a broken F-Droid build holds back only
Linux and Windows packages, which keeps the release a draft. Preparation patches source with F-Droid and `fdroid-sign`, not the desktop packages or the release. Preparation patches source with
exact-match replacements, so it breaks quietly when the files it rewrites change. The step is slow exact-match replacements, so it breaks quietly when the files it rewrites change. The step is slow
because it installs and builds from scratch. because it installs and builds from scratch.

2
scripts/release/ci.mjs
View file

@ -5,4 +5,4 @@ import desktop from "./steps/desktop.mjs"
import fdroid from "./steps/fdroid.mjs" import fdroid from "./steps/fdroid.mjs"
import gitea from "./steps/gitea.mjs" import gitea from "./steps/gitea.mjs"
await release("pnpm release:ci", [fdroid, desktop, gitea]) await release("pnpm release:ci", [desktop, gitea, fdroid])