ci(mobile): tag-only SemVer pipeline → Play internal, no GitHub releases#22
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
aneebbaig
changed the title
aneebbaig
changed the title
Rework mobile delivery for Google Play internal testing, no GitHub Releases: - On push to main touching apps/mobile, analyse Conventional Commits since the last tag, bump SemVer (feat→minor, fix→patch, BREAKING→ major), push a vX.Y.Z tag, build a signed AAB, deploy to the Play internal track (r0adkll/upload-google-play, gated on the PLAY_SERVICE_ACCOUNT_JSON secret). No feat/fix ⇒ no release. - Single AAB build (all ABIs; Play splits per-device); dropped the APK. - Tagging + build live in one workflow so the GITHUB_TOKEN-tag-doesn't- trigger-a-second-workflow trap is avoided (no PAT needed). - workflow_dispatch builds the current pubspec version on demand — used to mint the first v1.0.0 bootstrap AAB before Play auto-deploy exists. - AAB is a workflow artifact only, never a GitHub Release. - Branding guard reads the label from the AAB via bundletool. chore(mobile): reset version to 1.0.0+1 (fresh SemVer start) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015zEH6N4TpnwYyXhX4gSjrV
aneebbaig
added a commit
that referenced
this pull request
Jul 12, 2026
ci(mobile): tag-only SemVer pipeline → Play internal, no GitHub releases
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
Replace the tag-triggered APK→GitHub-Release flow with a Conventional-Commits SemVer pipeline that deploys to Google Play internal testing and never creates a GitHub Release.
Pipeline (
.github/workflows/mobile-release.yml)maintouchingapps/mobile/**→ analyse commits since last tag → bump SemVer (feat→minor,fix→patch,BREAKING→major) → pushvX.Y.Ztag → build signed AAB → deploy to Playinternal. Nofeat/fix⇒ no release.workflow_dispatchbuilds the current pubspec version on demand → mints the first v1.0.0 bootstrap AAB.permissions: contents: write(only to push tags/version).r0adkll/upload-google-play, gated onPLAY_SERVICE_ACCOUNT_JSONso builds pass pre-bootstrap.bundletool.Versioning reset
1.0.0+1.One-time manual bootstrap (Play side, only you can do)
com.anhib.align, set up Internal testing track, add yourself as tester.workflow_dispatchrun) and upload it manually (enrolls Play App Signing).PLAY_SERVICE_ACCOUNT_JSON.feat/fixmerged tomainauto-bumps, builds, and deploys to Play.🤖 Generated with Claude Code