fix: use publish-android task for Play Store deploy (stamps + signs + uploads)

The old workflow built with build-android-bundle (debug-signed) then uploaded
separately. publish-android stamps the versionCode, re-signs with the release
keystore, and uploads in one Dagger call.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Thomas SharedInbox
2026-05-18 16:42:23 +02:00
co-authored by Claude Sonnet 4.6
parent 02e8c2200a
commit 8319002e0c
+2 -7
View File
@@ -105,18 +105,13 @@ jobs:
DAGGER_CLIENT_KEY: ${{ secrets.DAGGER_CLIENT_KEY }}
run: scripts/setup_dagger_remote.sh
- name: Build Android Bundle
- name: Publish Android to Play Store
env:
ANDROID_KEYSTORE_BASE64: ${{ secrets.ANDROID_KEYSTORE_BASE64 }}
ANDROID_KEYSTORE_PASSWORD: ${{ secrets.ANDROID_KEYSTORE_PASSWORD }}
DAGGER_NO_NAG: "1"
run: task build-android-bundle
- name: Upload to Play Store
env:
PLAY_STORE_CONFIG_JSON: ${{ secrets.PLAY_STORE_CONFIG_JSON }}
DAGGER_NO_NAG: "1"
run: task upload-android-bundle
run: task publish-android
- name: Build & Deploy APK to server
continue-on-error: true