gplay-release-flow
gplay release flow
Drive the Google Play release lifecycle from the command line with gplay:
upload a build to a track, promote it up the ladder, run a staged
rollout on production (and halt / resume / complete it), and list
what is currently on a track. gplay hides Google's three-step Edit transaction
(edits.insert → change → edits.commit) behind a single call per command.
Shared conventions (auth setup with gplay auth doctor, --package pinning
via gplay init, --output json for machines, and the semantic exit-code
table) are in gplay-cli-usage; onboarding auth is gplay-setup. The codes
that matter most here: 3 a required --confirm is missing (re-run with it),
30 an API 4xx such as a missing track, 60 an ambiguous target (two releases
coexist), 40/50 retry-safe (5xx / network).