Publish Google Play drafts through Fastlane and release CI - #37
Merged
Merged
Conversation
APK artifacts
Built from commit |
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
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.
Adds
bundle exec fastlane android play_releaseto upload a signed release AAB and its matching native debug symbols to Google Play. Local uploads default to an internal-track draft, with explicit track/status overrides and API validation without committing a release.The existing tag-triggered release workflow now builds and verifies artifacts, publishes the GitHub Release, then uploads an internal Google Play draft. Play upload failures fail the workflow while leaving the GitHub Release available. The standard
SUPPLY_JSON_KEY_DATAenvironment variable carries the complete service-account JSON for both local runs and the release upload step, which receives the matching repository Actions secret. PR workflows receive no Play credentials.The lane validates parameters, credential structure and input files before upload. Store listing metadata and artwork are skipped. English and Russian documentation covers account setup, local env usage and the automated release flow.
Validation:
git diff --checkpassed.play_release track:internal release_status:draft validate_only:true: checksummed AAB versionCode 12000 and matching native symbols uploaded, internal-track edit validated successfully, no release committed. The release workflow itself was not triggered.