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/asc-skills
asc-cli-usage
Guidance for using asc cli in this repo (flags, output formats, pagination, auth, and discovery). Use when asked to run or design asc commands or interact with App Store Connect via the CLI.
760asc-metadata-sync
Sync, validate, and apply App Store metadata with the current asc canonical metadata workflow. Use when updating metadata, localizations, keywords, or migrating legacy fastlane metadata.
712asc-id-resolver
Resolve App Store Connect IDs (apps, builds, versions, groups, testers) from human-friendly names using asc. Use when commands require IDs.
693asc-release-flow
Determine whether an app is ready to submit, then drive the current App Store release flow with asc, including validation, staging, review submission, first-time availability, subscriptions, IAP, Game Center, and App Privacy checks.
692asc-submission-health
Validate App Store submission readiness, submit prepared versions, and monitor review status with current asc commands. Use when shipping or troubleshooting review submissions.
686asc-testflight-orchestration
Orchestrate TestFlight distribution, groups, testers, and What to Test notes using asc. Use when rolling out betas.
677