Skip to content

K2GO-572 chore(release): v1.2.0 final release, versionCode update - #803

Merged
luisguzman-adfa merged 2 commits into
mainfrom
chore/K2GO-572-v1.2.0-final
Nov 17, 2026
Merged

luisguzman-adfa merged 2 commits into
mainfrom
chore/K2GO-572-v1.2.0-final

Conversation

@luisguzman-adfa

Copy link
Copy Markdown
Collaborator

What changes

  • build.gradle: versionName v1.2.0, versionCode 1020099 (APK and Play code 10200990).
  • Button 2 (play-release.yml): runs from main and tags the final commit v1.2.0 after checking that the approved candidate (v1.2.0-rc.3) is the newest rc. It does not touch Google Play.
  • check-release also refuses a versionCode that does not match versionName.

Why

  • Release v1.2.0 on GitHub, the website, R2 and OTA. Before this, button 2 refused every rc commit.

Steps to QA

  • Baseline (main): button 2 with v1.2.0-rc.3 stops, because the rc commit says v1.2.0-rc.3.
  • Change: with the live tags, final-tag gives v1.2.0 and check-release passes; a wrong versionCode is refused.

Verifications

  • 29 unit tests in tools/play-publish pass.
  • OTA notes: the ## v1.2.0 entry is unchanged.

Notes

  • After merge: run "Play: 2. publish release" from main with v1.2.0-rc.3. Sending the final build to Play Production is a later step.

@luisguzman-adfa
luisguzman-adfa merged commit be516ba into main Nov 17, 2026
4 checks passed
@luisguzman-adfa
luisguzman-adfa deleted the chore/K2GO-572-v1.2.0-final branch November 17, 2026 20:13
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