-
Notifications
You must be signed in to change notification settings - Fork 0
[HT-58]: Add the Play (AAB) leg to the release CI #92
Copy link
Copy link
Open
Labels
⚡ p1High-priority work needed for the next meaningful milestone or core gameplay path.High-priority work needed for the next meaningful milestone or core gameplay path.🙋 hitlRequires human-in-the-loop judgment for rules, naming, design, tone, or product behavior.Requires human-in-the-loop judgment for rules, naming, design, tone, or product behavior.🚦 ciGitHub Actions, analysis/test automation, build checks, release checks, or toolchain health.GitHub Actions, analysis/test automation, build checks, release checks, or toolchain health.🧩 featureA vertical slice that delivers user-visible behavior or playable product capability.A vertical slice that delivers user-visible behavior or playable product capability.🧭 needs triageNot yet accepted into active work; needs prioritization, labels, scope, or owner review.Not yet accepted into active work; needs prioritization, labels, scope, or owner review.
Description
Metadata
Metadata
Assignees
Labels
⚡ p1High-priority work needed for the next meaningful milestone or core gameplay path.High-priority work needed for the next meaningful milestone or core gameplay path.🙋 hitlRequires human-in-the-loop judgment for rules, naming, design, tone, or product behavior.Requires human-in-the-loop judgment for rules, naming, design, tone, or product behavior.🚦 ciGitHub Actions, analysis/test automation, build checks, release checks, or toolchain health.GitHub Actions, analysis/test automation, build checks, release checks, or toolchain health.🧩 featureA vertical slice that delivers user-visible behavior or playable product capability.A vertical slice that delivers user-visible behavior or playable product capability.🧭 needs triageNot yet accepted into active work; needs prioritization, labels, scope, or owner review.Not yet accepted into active work; needs prioritization, labels, scope, or owner review.
Parent
Parent: #89
What to build
Extend the existing Release Please pipeline to publish an Android App Bundle
(AAB) to Google Play. Release Please already does versioning, changelog, tag,
GitHub prerelease, and a signed APK → GitHub Release; only the Play leg is
missing — Play needs an AAB, not an APK.
Signing enrollment, a Play Developer API service account (new repo
secret), and the one-time manual first AAB upload (Play requires it before
API uploads unlock).
release_created, alsoflutter build appbundle(reusing the existing keystore secrets) and upload the AAB to thePlay closed-test track via service account (
r0adkll/upload-google-playor fastlane
supply). Keep the existing APK → GitHub Release step for sideload.Acceptance criteria
closed-test track.
uploaded.
docs/workflows/release.mdupdated to document the Play leg.flutter analyzepasses.Blocked by
None for the workflow code. The live Play upload requires owner Play Console +
service-account setup (can be wired/tested against the closed-test track once
available).