android-release

Prepares Fedi Android releases on Google Play via the publishing API and stages public APK releases.

78|27|Updated May 4, 2024
One-click install
npx skills add https://github.com/fedixyz/fedi --skill android-release-fedixyz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-release
Source: https://github.com/fedixyz/fedi/tree/main/.agents/skills/android-release
Command: npx skills add https://github.com/fedixyz/fedi --skill android-release-fedixyz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Preparing a Fedi Android release requires juggling the Google Play publishing API's edit model, track promotion, localized release notes, and a separate GitHub-based APK channel, all with hard gates that must never be crossed without explicit user approval. This Skill encodes that entire workflow so releases are staged correctly and safely. ## Core Features & Use Cases - Google Play draft preparation: Opens an edit, reads track state, stages a draft release on the production track with localized release notes, validates, and commits it as a console-visible draft. - Public APK release staging: Manages the draft GitHub release that carries the signed APK, stages release notes and report attachments, and verifies the tag target matches the build commit. - Safety gates: Enforces strict boundaries where rollouts, live release changes, and publishing are never agent actions and always require explicit user instruction. - Use Case: After CI uploads a new build to the internal track, ask the agent to prepare the 26.X.Y production release; it stages the draft with release notes on Google Play and updates the GitHub draft, then hands off with console and release links for the user to publish. ## Quick Start Ask the agent to prepare the Fedi Android production release for version 26.X.Y using the build CI uploaded to the internal track.

Frequently Asked Questions about android-release

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

FAQPage Schema
How do I promote an Android build from internal track to production on Google Play?

Open an edit through the Google Play publishing API, read the tracks to find the internal version code, then PUT a draft release with that version code onto the production track and commit the edit. The committed draft appears in the Play Console under Production, Releases, ready for review.

How do I authenticate with the Google Play publishing API using a service account?

Create a service account in the Google Cloud project linked to the Play Console, download its JSON key, and grant that account release permission in Play Console Users and permissions. The gp.sh script exchanges the key for an access token on each call via a JWT bearer assertion.

Can the agent publish or roll out a Google Play release automatically?

No. Committing a completed or inProgress release sends it straight to review for com.fedi, so rollout happens only on an explicit, separate user instruction. Managing a live rollout, such as raising userFraction or halting, is never an agent action.

Why does a Google Play API call return a 403 error?

A 403 means the Play Console grant for the service account is missing or too narrow, not that the key is bad. Invite the service account's email under Users and permissions in the Play Console and grant it release permission on the app.

What are the limitations of the Google Play publishing API for releases?

The API cannot roll back a live release, so fixes require a new version code through the whole pipeline. Release notes are capped at 500 characters per locale, userFraction is only valid with inProgress status, and edits expire if not committed.

Does this skill upload Android builds to Google Play?

No. CI owns the binary: the release-production.yml workflow builds and uploads the AAB to the internal track via fastlane. This skill picks up from there, promoting an already-uploaded build to production.