What App Studio owns
App Studio generates Google Play release plans from repo history and app metadata.
It can submit Play edits for tracks, release notes, listing fields, and uploaded artifacts.
ReleaseMind does not build Android artifacts; provide an AAB or APK when publishing binaries.
Set repo defaults
Save the package name and default language for each app repo.
Use base_tag and head_ref to control the release boundary for generated notes.
Validate-only mode lets you test a Play edit without committing it.
CLI and automation
Use si orbit releasemind play plan -R OWNER/REPO --base-tag v1.2.0 --json for planning.
Use si orbit releasemind play publish for Play publish requests.
Automation clients can call /api/automation/releases/play/plan and /api/automation/releases/play/publish.
Review and introspect
Play releases need product, QA, and store metadata to agree.
- Did the selected track match the intended rollout?
- Are release notes localized enough for your audience?
- Did validate-only succeed before committing a risky edit?