android-workflow-beta_skill
- Shell
1
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill hitoshura25/claude-devtools --skill android-workflow-beta- SKILL.md8.9 KB
Overview
This skill generates a GitHub Actions workflow for manual deployment to the Play Store beta (closed testing) track. It creates a deploy-beta.yml that runs tests, builds an AAB, and uses Fastlane to push either a full or staged rollout. The workflow includes artifact uploads, keystore handling, and service account injection for Play Console access.
How this skill works
The skill scaffolds a workflow with two jobs: test and deploy. The test job runs unit tests and uploads reports. The deploy job builds a release bundle, decodes the keystore from a secret, creates a service account file, and invokes Fastlane deploy lanes for full or staged rollouts. It cleans up sensitive files and uploads the AAB and mapping artifacts after deployment.
When to use it
- When you need a manual, auditable process for beta/alpha Play Store releases
- When you already use Fastlane lanes for Play Store deployments
- When you want configurable rollout types (full or staged) from the Actions UI
- When you require pinned action SHAs and CI test gating before deploy
- When you need artifact retention for AABs and mapping files for debugging
Best practices
- Ensure a Fastlane lane named deploy_beta exists and is verified locally with bundle exec fastlane lanes
- Store signing keystore and Play service account JSON in GitHub Secrets (base64 for keystore)
- Pin sensitive operations to run only after successful test job to avoid bad releases
- Start staged rollouts at a lower percentage and monitor Play Console crash and ANR reports for 24 hours
- Remove service account and keystore files in cleanup steps to avoid leaking secrets
Example use cases
- Run a manual beta release to validate a new feature with 100+ testers via the beta track
- Deploy a small alpha build to a limited group for early validation before wider beta
- Perform a staged rollout (e.g., 50%) to monitor stability before a full rollout
- Archive the built AAB and mapping file for future debugging or repeater builds
- Use as a template in CI to standardize Play Store beta deployments across multiple apps
FAQ
Fastlane configured with a deploy_beta lane, package name known, and GitHub Secrets for keystore and service account.
How do I run a staged rollout?
Trigger the workflow manually, set rollout_type to staged and specify rollout_percentage (0.05-1.0 values supported for fractional percentages).
What if the workflow reports 'Track not found'?
Create the corresponding alpha or beta closed testing track in the Play Console before running the workflow.
