diff --git a/README.md b/README.md
index 81df10af..0b906588 100644
--- a/README.md
+++ b/README.md
@@ -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
 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
-Linux and Windows packages, which keeps the release a draft. Preparation patches source with
+that apk the way F-Droid will. It runs last in CI, so a broken F-Droid build holds back only
+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
 because it installs and builds from scratch.
 
diff --git a/scripts/release/ci.mjs b/scripts/release/ci.mjs
index 027ee6bc..4aadb808 100644
--- a/scripts/release/ci.mjs
+++ b/scripts/release/ci.mjs
@@ -5,4 +5,4 @@ import desktop from "./steps/desktop.mjs"
 import fdroid from "./steps/fdroid.mjs"
 import gitea from "./steps/gitea.mjs"
 
-await release("pnpm release:ci", [fdroid, desktop, gitea])
+await release("pnpm release:ci", [desktop, gitea, fdroid])