makiolaj/calendula
1
0
Fork 1
Code Actions Releases 32 Activity

ci(release): fix the Play handoff and stop it killing releases

Browse Source 
actions/upload-artifact@v4 reads any non-github.com forge as GHES and
refuses to run, so the AAB handoff failed on Gitea and took the whole
2.17.0 release down with it — the step sat before the F-Droid publish
without continue-on-error, so no APK shipped, no tag, no Codeberg
release.

Switch both sides to the patched fork (pinned to a commit), move the
AAB build + handoff to the end of the release job, and make both
non-fatal.
This commit is contained in:
Jean-Luc Makiola
2026-07-30 22:38:28 +02:00
parent e8657117d6
commit 4d990e3749
2 changed files with 53 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/RELEASING.md
View File

@@ -113,7 +113,13 @@ the only one that gets a different artifact and a different signature.
**Artifact.** Play takes an **App Bundle** (`bundleRelease`), not the APK. It is
a second output of the same source and the same signing config — never a
repackage of the published APK, which stays untouched so the F-Droid
reproducibility guarantee is unaffected. `dependenciesInfo` stays disabled for
reproducibility guarantee is unaffected. The bundle is built at the very **end**
of the `release` job, after everything else has shipped, and both it and the
handoff to the `play` job are `continue-on-error` — nothing Play-related may
take down a release that is already published. The handoff uses a patched
`upload-artifact`/`download-artifact` fork pinned to a commit: the official v4
actions read any non-github.com forge as an unsupported GHES instance and refuse
to run on Gitea (go-gitea/gitea#36024). `dependenciesInfo` stays disabled for
the bundle too; Play's "app dependencies" report is optional and re-enabling it
would break reproducibility.