One release ships everything: Play, App Store, meshplus.apk and the F-Droid merge request #3

Merged

backmeupplz merged 1 commit from release-pipeline into main

2026-10-16 19:28:52 +00:00

backmeupplz commented

2026-10-16 19:01:46 +00:00

(Migrated from github.com)

A published GitHub release vX.Y.Z now ships Mesh+ everywhere. The scripts are the ones in absplus PR #34 (.github/scripts, identical), with Mesh+ values in the workflow env.

Google Play: the play-flavor bundle goes to production with the changelog as release notes. play.py replaces r0adkll and withdraws a release still in review (changesInReviewBehavior=CANCEL_IN_REVIEW_AND_SUBMIT).
App Store: ios/release.sh (now with NO_UPLOAD=1 for dry runs), then appstore.py, which waits for processing and cancels a submission still waiting or in review. On the first release it renames the pending "1.0" version to 0.4.4 and attaches build 8. There's no What's New on an app's first version. It submits with automatic release.
meshplus.apk (fdroid flavor) is attached as before, so meshplus.app's releases/latest/download/meshplus.apk keeps working. F-Droid MR !51979 is brought up to the release while it's open.
Manual runs: dry-run builds both apps and publishes nothing; testflight-only uploads the iPhone build.
A Play or F-Droid failure doesn't block the other, and a step whose secret is missing is skipped with a warning (ASC_KEY_P8, GITLAB_TOKEN).

Tested locally:

the script checks;
NO_UPLOAD=1 ios/release.sh 0.4.4 8 gives MeshPlus.ipa 0.4.4 (8), not uploaded;
appstore.py --dry-run: rename 1.0 to 0.4.4 (PREPARE_FOR_SUBMISSION), first version, submit;
fdroid.py --dry-run: the 0.4.3 → 0.4.4 diff on !51979.

🤖 Generated with Claude Code

A published GitHub release `vX.Y.Z` now ships Mesh+ everywhere. The scripts are the ones in absplus PR #34 (`.github/scripts`, identical), with Mesh+ values in the workflow env. - **Google Play:** the play-flavor bundle goes to production with the changelog as release notes. `play.py` replaces r0adkll and withdraws a release still in review (`changesInReviewBehavior=CANCEL_IN_REVIEW_AND_SUBMIT`). - **App Store:** `ios/release.sh` (now with `NO_UPLOAD=1` for dry runs), then `appstore.py`, which waits for processing and cancels a submission still waiting or in review. On the first release it renames the pending "1.0" version to 0.4.4 and attaches build 8. There's no What's New on an app's first version. It submits with automatic release. - **meshplus.apk** (fdroid flavor) is attached as before, so meshplus.app's `releases/latest/download/meshplus.apk` keeps working. F-Droid MR !51979 is brought up to the release while it's open. - **Manual runs:** `dry-run` builds both apps and publishes nothing; `testflight-only` uploads the iPhone build. - A Play or F-Droid failure doesn't block the other, and a step whose secret is missing is skipped with a warning (`ASC_KEY_P8`, `GITLAB_TOKEN`). Tested locally: - the script checks; - `NO_UPLOAD=1 ios/release.sh 0.4.4 8` gives MeshPlus.ipa 0.4.4 (8), not uploaded; - `appstore.py --dry-run`: rename 1.0 to 0.4.4 (PREPARE_FOR_SUBMISSION), first version, submit; - `fdroid.py --dry-run`: the 0.4.3 → 0.4.4 diff on !51979. 🤖 Generated with [Claude Code](https://claude.com/claude-code)