suede-play-release

Automates Google Play Android releases with fastlane uploads, track promotion, and API readback verification.

123|10|Updated May 24, 2026
One-click install
npx skills add https://github.com/JasonColapietro/suede-creator-skills --skill suede-play-release-jasoncolapietro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: suede-play-release
Source: https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-play-release
Command: npx skills add https://github.com/JasonColapietro/suede-creator-skills --skill suede-play-release-jasoncolapietro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyjwt, cryptography, and includes scripts (resource) components.

What problem does it solve? Shipping an Android release through Google Play involves fragile steps: credentials that silently lack permissions, changelogs that silently go missing, and fastlane summaries that report success without proving what is actually live. This Skill walks an agent through the full delivery pipeline and verifies every claim against the Play Developer API. ## Core Features & Use Cases - Credential preflight: Runs a script that opens and deletes a real Play edit to prove the service account, token exchange, and Play Console grant all work before any release action. - Safe release pipeline: Enforces pull-before-run, per-locale per-versionCode changelogs, AAB signature and manifest verification, testing-track upload, and promotion of the exact validated versionCode instead of re-uploading. - Live-state readback: Reads the production track from the Play API and reports versionCode, status, and userFraction, distinguishing a staged rollout from a completed one. - Use Case: You have a signed AAB ready and want to promote it from internal testing to a 10% production rollout. The Skill preflights the credential, verifies the artifact, promotes the existing versionCode, pauses for your explicit confirmation, then reads the track back to confirm the staged rollout actually landed. ## Quick Start Use the suede-play-release skill to upload my Android AAB to the internal track and then promote versionCode 42 to production at 10 percent, verifying the live track state afterward.

Frequently Asked Questions about suede-play-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upload an Android AAB to Google Play from the command line?

Use fastlane supply lanes to upload the AAB to a testing track such as internal, then promote that same versionCode to production with track_promote_to instead of re-uploading. Play rejects a second bundle carrying a versionCode it already has.

How do I set up a Google Play service account for publishing?

Create a dedicated publishing service account separate from any billing account, store its JSON base64-encoded in the macOS Keychain, then invite its email in Play Console under Users and permissions with release permissions. The Console grant is a UI action that cannot be done from the API.

Why does my Play release show old release notes after uploading?

A missing changelog file for a versionCode is a silent skip, not an error, so Play serves the previous version's notes. Write one changelog file per locale per versionCode under fastlane/metadata/android before uploading.

Why does a new Google Play service account return 403?

A 403 on a brand-new service account is the normal state before the Play Console grant. The key itself can be valid while Play has not granted it access; invite the service-account email in the Console and re-run the preflight.

Can this skill handle iOS App Store releases or app building?

No. It covers only Google Play delivery for Android. Building and testing the app belongs to android-app-factory, listing audits to suede-aso, and iOS release to a separate companion skill not in this pack.