gps-release

Play release flow

1. Confirm package name and artifact (.aab preferred).
2. Deploy to a testing track first:

gps --package $PKG deploy --file $AAB --track internal --release-notes "$NOTES" --confirm

1. Promote when ready:

gps --package $PKG tracks promote --from internal --to beta --confirm
gps --package $PKG tracks promote --from beta --to production --user-fraction 0.1 --confirm

1. Read the lifecycle state for the exact version:

gps --package $PKG tracks releases production --version-code $VERSION_CODE --json

1. Expand or halt:

gps --package $PKG tracks list --json
gps --package $PKG tracks rollout production --user-fraction 0.5 --confirm
gps --package $PKG tracks halt production --confirm

Rules

• Never skip --confirm on writes.
• Prefer internal/alpha before production.
• Use --validate-only when dry-running supported commands.
• Publish approved managed releases in Play Console.
• MCP: gps_deploy_app, gps_promote_release, gps_list_release_summaries, gps_update_rollout, gps_halt_release.