Automate this: /mobile-release:ship-beta uploads to the internal track; /mobile-release:ship-release handles production and the staged-rollout decision, gating on approval before anything irreversible. What is safe to re-run: skills/release-automation/references/idempotency.md.

Upload signed Android artifacts to Google Play and move them between tracks. Execute the steps in order. Load only the reference you need.

Confidence marks used throughout this skill and its references: [verified] — read off a primary vendor source on 2026-08-05. [snippet] — secondary source only, plausible but unconfirmed. [unverified] — not confirmed anywhere; run the check given before relying on it.

Publish process:

Confirm the artifact is a signed .aab and that the release is buildable. Do not attempt an upload against an unsigned or debug-signed bundle.
Set up and verify service-account authentication using references/service-account.md.
Pick one upload path and stay on it: fastlane supply (references/fastlane-supply.md), raw Publishing API v3 (references/publishing-api-v3.md), or the r0adkll/upload-google-play GitHub Action (references/github-actions.md).
Choose the track, release status, and rollout fraction using references/tracks-and-rollout.md.
Upload the R8/ProGuard mapping and native debug symbols using references/mapping-and-symbols.md.
Commit the edit. Nothing is live until commit succeeds.
Verify the release landed on the intended track. On any failure, diagnose with references/troubleshooting.md before retrying — do not blindly re-run.

Before publishing anything to a public track, run the play-store-listing skill. Upload succeeds long before the listing is compliant.

play-store-publish