Gpd Release Flow

What it does

This skill automates release workflows for Google Play (GPD). It enables an AI agent to upload builds, publish releases to different tracks (internal, beta, production), manage rollouts, and perform actions like halting or rolling back deployments. The skill streamlines the deployment process and reduces manual errors associated with managing Google Play app updates.

When to use it

• You need to upload a new Android App Bundle (.aab) file for release.
• You want to publish an application to a specific track (e.g., internal testing, beta distribution, production release).
• You require precise control over the release process involving multiple changes and edits.
• You need to manage staged rollouts or halt/rollback existing releases.

Key capabilities

• Uploads builds using gpd publish upload.
• Releases applications to tracks with specified statuses (e.g., draft, completed) using gpd publish release.
• Promotes applications between tracks using gpd publish promote.
• Creates, validates and commits edit lifecycles for complex releases using gpd publish edit commands.
• Manages staged rollouts by adjusting the rollout percentage using gpd publish rollout.
• Halts or rolls back releases using gpd publish halt and gpd publish rollback.
• Checks track status with gpd publish status and lists available tracks with gpd publish tracks.

Example prompts

• "Upload the app bundle 'app.aab' for com.example.app."
• "Release version 123 of com.example.app to the production track with a staged rollout starting at 5%."
• “Promote com.example.app from the beta track to the production track.”

Tips & gotchas

• Ensure GPD_SERVICE_ACCOUNT_KEY credentials are properly configured before using this skill.
• Always use a new version code for each upload.
• Explicitly specify --package with each command to avoid ambiguity.
• Use the --status draft flag initially for potentially risky releases.