Overview

This skill helps you manage Google Play build state, processing status, and retention using gpd publish. Use it when waiting on processing or managing releases across internal, production, or rollback scenarios.

How This Skill Works

It orchestrates gpd publish commands to upload and validate builds, query release status across tracks, inspect recent tracks, and perform safe cleanup or fast distribution via internal sharing. It emphasizes following an end-to-end release flow and incrementing the versionCode for each upload.

When to Use It

• Uploading a new AAB and waiting for processing
• Checking status for internal and production tracks
• Reviewing recent tracks and releases for a package
• Distributing a build quickly via internal sharing
• Halt or rollback a release on production

Quick Start

1. Step 1: Prepare your AAB and run gpd publish upload app.aab --package com.example.app
2. Step 2: Check status with gpd publish status --package com.example.app --track internal and view tracks
3. Step 3: If needed, share internally with gpd publish internal-share upload app.aab --package com.example.app or halt/rollback with --confirm

Best Practices

• Use a new versionCode for every uploaded build
• Prefer gpd publish release flow over manual steps
• Validate upload by inspecting status and tracks
• Use internal sharing for fast testing before full release
• Always confirm halts or rollbacks to avoid accidental releases

Example Use Cases

• gpd publish upload app.aab --package com.example.app
• gpd publish status --package com.example.app --track internal
• gpd publish tracks --package com.example.app
• gpd publish internal-share upload app.aab --package com.example.app
• gpd publish halt --package com.example.app --track production --confirm

Frequently Asked Questions