ci(deploy): add Google Play API deployment workflow#73
Merged
Conversation
Bypasses the recurring Play Console UI loop bug that prevents submitting production releases for review by uploading the AAB directly via the Google Play Developer Publishing API (r0adkll/upload-google-play action). Triggered manually via workflow_dispatch with configurable track, rollout percentage and release status. Reuses existing signing secrets (KEYSTORE_BASE64, KEYSTORE_PASSWORD, KEY_PASSWORD, KEY_ALIAS) and adds GOOGLE_PLAY_SERVICE_ACCOUNT_JSON for API authentication.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.github/workflows/deploy-google-play.ymlto bypass the recurring Play Console UI loop bug that blocks production release submissions.r0adkll/upload-google-play@v1(Google Play Developer Publishing API) for direct AAB upload.workflow_dispatchwith configurabletrack,rollout_percentage, andstatus.Secrets required
Already configured in the repo:
KEYSTORE_BASE64,KEYSTORE_PASSWORD,KEY_PASSWORD,KEY_ALIAS(reused from existing release workflow)GOOGLE_PLAY_SERVICE_ACCOUNT_JSON(new — service accountplay-publisher@simple-notes-sync-deploy.iam.gserviceaccount.com, granted Release Manager in Play Console)Why
The Play Console UI has a known intermittent bug that prevents pressing "Send for review" on production releases — last release (v2.5.0) required a Google support call. v2.5.1 hits the same bug. API path is more reliable long-term.
Test plan
After merge, trigger workflow with
track=production,status=draft,rollout_percentage=100to upload v2.5.1 as a draft (no live publish), then verify in Play Console and click Publish.