Release flow (Internal, Beta, Production)

Use this skill when you need to get a new build onto Google Play Store.

Preconditions

•Ensure credentials are set (gplay auth login or GPLAY_SERVICE_ACCOUNT env var).
•Build must be an AAB (App Bundle) or APK.
•Version code must be higher than previous releases.
•Service account needs "Release Manager" permission in Play Console.

Android Release

Preferred end-to-end commands

Internal track (for internal testing):

bash

gplay release \
  --package com.example.app \
  --track internal \
  --bundle app-release.aab

Beta track (for beta testers):

bash

gplay release \
  --package com.example.app \
  --track beta \
  --bundle app-release.aab \
  --release-notes @release-notes.json

Production with staged rollout (gradual release):

bash

gplay release \
  --package com.example.app \
  --track production \
  --bundle app-release.aab \
  --release-notes @release-notes.json \
  --rollout 10

Manual sequence (when you need more control)

•

Create edit session:

bash

EDIT_ID=$(gplay edits create --package com.example.app | jq -r '.id')

•

Upload bundle:

bash

gplay bundles upload \
  --package com.example.app \
  --edit $EDIT_ID \
  --file app-release.aab

•

Update track:

bash

gplay tracks update \
  --package com.example.app \
  --edit $EDIT_ID \
  --track production \
  --json @track-config.json

•

Validate edit:

bash

gplay edits validate --package com.example.app --edit $EDIT_ID

•

Commit edit (publishes changes):

bash

gplay edits commit --package com.example.app --edit $EDIT_ID

Track Promotion

Promote a release from one track to another:

bash

# Promote from internal to beta
gplay promote \
  --package com.example.app \
  --from internal \
  --to beta

# Promote from beta to production with 25% rollout
gplay promote \
  --package com.example.app \
  --from beta \
  --to production \
  --rollout 25

Staged Rollout Management

Start with 10% rollout:

bash

gplay release \
  --package com.example.app \
  --track production \
  --bundle app.aab \
  --rollout 10

Increase to 50%:

bash

gplay rollout update \
  --package com.example.app \
  --track production \
  --rollout 50

Halt rollout (pause distribution):

bash

gplay rollout halt --package com.example.app --track production

Resume rollout:

bash

gplay rollout resume --package com.example.app --track production

Complete rollout (release to 100%):

bash

gplay rollout complete --package com.example.app --track production

Release Notes Format

release-notes.json:

json

{
  "en-US": "Bug fixes and performance improvements",
  "es-ES": "Correcciones de errores y mejoras de rendimiento",
  "fr-FR": "Corrections de bugs et améliorations des performances"
}

Pre-release Checklist

Before releasing, verify:

• Version code is incremented
• AAB/APK is signed with correct keystore
• ProGuard/R8 mapping files uploaded (for crash reports)
• Release notes written for all locales
• Testing completed on internal/beta track
• Service account has correct permissions

Common Release Strategies

Strategy 1: Internal → Beta → Production

bash

# Week 1: Internal
gplay release --package com.example.app --track internal --bundle app.aab

# Week 2: Beta (after testing)
gplay promote --package com.example.app --from internal --to beta

# Week 3: Production with staged rollout
gplay promote --package com.example.app --from beta --to production --rollout 10
gplay rollout update --package com.example.app --track production --rollout 50  # Day 2
gplay rollout complete --package com.example.app --track production            # Day 7

Strategy 2: Direct to Production with Staged Rollout

bash

# Day 1: 10%
gplay release --package com.example.app --track production --bundle app.aab --rollout 10

# Day 2: 25%
gplay rollout update --package com.example.app --track production --rollout 25

# Day 3: 50%
gplay rollout update --package com.example.app --track production --rollout 50

# Day 7: 100%
gplay rollout complete --package com.example.app --track production

Notes

•Always use --help to verify flags for the exact command.
•Use --output table for human-readable output; default is JSON.
•For CI/CD, use GPLAY_SERVICE_ACCOUNT environment variable.
•Upload deobfuscation files after each release for crash symbolication.