gpd-release-flow
Release flow (Google Play)
Use this skill when you need to upload a build, publish to a track, or manage rollout.
Preconditions
- Ensure credentials are set (
GPD_SERVICE_ACCOUNT_KEY). - Use a new version code for each upload.
- Always pass
--packageexplicitly.
Preferred end-to-end commands
Upload and release to a track
gpd publish upload app.aab --package com.example.app
gpd publish release --package com.example.app --track internal --status completed
Promote between tracks
More from rudrankriyam/gpd-cli-skills
gpd-cli
Manage Google Play Developer Console using the gpd CLI. Use when working with Android app publishing, Play Store releases, app reviews, Android vitals, in-app purchases, subscriptions, or when the user mentions Google Play, Play Store, Android publishing, or gpd.
35gpd-cli-usage
Guidance for using the Google Play Developer CLI (flags, output formats, auth, pagination). Use when asked to run or design gpd commands for Play Console workflows.
34gpd-metadata-sync
Sync and validate Google Play metadata, listings, and assets with gpd, including Fastlane-style workflows. Use when updating store listings or translations.
32gpd-betagroups
Orchestrate Google Play beta testing groups and distribution using gpd. Use when managing testers, internal testing, or beta rollouts.
31gpd-id-resolver
Resolve Google Play identifiers (package, tracks, version codes, products, subscriptions) using gpd. Use when commands require IDs or exact values.
31gpd-ppp-pricing
Set region-specific pricing for Google Play subscriptions and products using gpd monetization commands. Use when adjusting prices by territory or PPP strategy.
31