← ClaudeAtlas

gplay-release-flowlisted

Ship Android releases through Google Play with `gplay releases`. Use when uploading an AAB or APK to a track, promoting a build up the track ladder, steering a staged rollout, inspecting or downloading what a track holds, building a system APK for a device image, attaching a ProGuard/R8 mapping, sharing a build via Internal App Sharing, or managing legacy OBB expansion files.
PollyGlot/google-play-cli-skills · ★ 5 · AI & Automation · score 77
Install: claude install-skill PollyGlot/google-play-cli-skills
# gplay release flow Shared conventions are in `gplay-cli-usage`; onboarding auth is `gplay-setup`. ## Mental model: the track ladder + the rollout state machine A build is uploaded to one **track** (`internal`, `alpha`, `beta`, `production`, or any custom closed-track name) and then **promoted** up the ladder: the same `versionCode`, no AAB re-upload. On a track, the latest release moves through a small state machine: ``` draft ──► inProgress (userFraction f, 0 < f < 1) ──► completed (no fraction) │ ▲ halt│ │resume ▼ │ halted (fraction preserved) ``` `rollout` sets the fraction, `halt` freezes it, `resume` un-freezes it, and `complete` ramps to 100%. `--staged` takes a fraction strictly between 0 and 1: `--staged 1.0` exits `2` before any call; a full rollout is `--complete` (on `upload`/`promote`) or `releases complete`. When a track holds two releases (e.g. `inProgress` plus `halted`), every verb refuses to guess (exit `60`): pin one with `--version-code` or `--release-name`. ## Upload a build to a track ```bash gplay releases upload ./app.aab --track internal gplay releases upload ./app.aab --track production --staged 0.1 --confirm gplay releases upload ./app.aab --track production --complete --confirm ``` Any string is a valid `--track`, but the track must already exist (see *Track must exist first* below). Flags: `gplay releases upload --help`. AAB/APK uploads are resumable: a transient interruption resu