Skip to content

K2GO-564 feat(release): button 2 sends the final AAB to Play, then tags and releases - #804

Merged
luisguzman-adfa merged 2 commits into
mainfrom
feat/K2GO-564-release-to-play
Nov 17, 2026
Merged

luisguzman-adfa merged 2 commits into
mainfrom
feat/K2GO-564-release-to-play

Conversation

@luisguzman-adfa

Copy link
Copy Markdown
Collaborator

What changes

  • Button 2 (play-release.yml) builds the final AAB and sends it to the Play beta track (Open testing). Only after Play accepts the upload, it tags the commit and runs the release build (GitHub Release, website, R2, OTA).
  • play_publish.py: final-plan replaces final-tag. One step gives the release tag, checks versionName, reads the release notes and gives the versionCode base.
  • Workflow names: App+Play: 1. send candidate to Play Console and App+Play: 2. publish release. The button 1 summary points to button 2.
  • ADR point 4 describes the new button 2.

Why

  • The final version reaches Play with its own name (v1.2.0), not the rc name. One button publishes a final version to every channel.

Steps to QA

  • Baseline (main): button 2 tags and releases, but sends nothing to Play.
  • Change: final-plan on main gives tag=v1.2.0 and code_base=1020099. It refuses an older rc and a commit whose versionName is an rc.

Verifications

  • 29 unit tests in tools/play-publish pass. Both workflow files parse as YAML.
  • The Play steps are the same as in button 1, which sent v1.2.0-rc.3.

Notes

  • The Play steps are now in both buttons. A shared action can follow.
  • If Play accepts the upload but the tag push fails, a re-run stops at the versionCode check. Recovery is manual.

…gs and releases

The final version reaches Play Open testing with its own name, and GitHub, R2 and OTA publish only after Play accepts the upload.
@luisguzman-adfa
luisguzman-adfa merged commit af77ac1 into main Nov 17, 2026
3 checks passed
@luisguzman-adfa
luisguzman-adfa deleted the feat/K2GO-564-release-to-play branch November 17, 2026 18:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant