Skip to content

K2GO-572 chore(release): v1.2.0-rc.2 (versionCode 73), rc label in versionName - #779

Merged
luisguzman-adfa merged 2 commits into
mainfrom
fix/K2GO-572-v1.2.0-rc.2
Nov 14, 2026
Merged

luisguzman-adfa merged 2 commits into
mainfrom
fix/K2GO-572-v1.2.0-rc.2

Conversation

@luisguzman-adfa

Copy link
Copy Markdown
Collaborator

What changes

  • versionName carries the rc label: v1.2.0-rc.2, versionCode 73 (Play 730).
  • OTA notes for v1.2.0 add the single-APK line.
  • play_publish.py: plan requires versionName to be the next candidate; new check-release refuses a build whose versionName is not the exact final tag.
  • play-release.yml and android-release-build.yml run check-release before any tag, build or upload. play-candidate.yml tags its versionName.
  • ADR-K2GO-564 updated to this rule.

Why

  • A binary must say what it is. An rc build is never released as final.

Verifications

  • 26 unit tests pass. Dry run: plan -> v1.2.0 / v1.2.0-rc.2 / 73 once v1.2.0-rc.1 is tagged; check-release v1.2.0 -> refused.
  • Output names: K2Go-v1.2.0-rc.2-release.apk, K2Go-v1.2.0-rc.2-play-release.aab.

Notes

  • play-release refuses every rc commit until the final-build step exists (K2GO-564).
  • rc.1 (720) was built from 3c71ae0 before this change; tag that commit v1.2.0-rc.1.

…rsionName

The binary, Play release and R2 files name the candidate they are. Notes add the single-APK line.
versionName carries the build label. play-candidate tags its versionName as the next rc; play-release and the release build refuse a commit whose versionName is not the exact final tag.
@luisguzman-adfa
luisguzman-adfa merged commit 7c27a80 into main Nov 14, 2026
4 checks passed
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