unom/punktfunk
8
0
Fork 1
Code Issues 4 Pull Requests Actions 1 Packages Projects Releases 51 Wiki Activity

Android canary ships to Play open + closed testing instead of internal #234

Merged
enricobuehler merged 2 commits from worktree-android-canary-open-testing into main 2026-08-14 19:50:44 +00:00
Conversation 0 Commits 2 Files Changed 5
+39 -15
2 Commits
Author SHA1 Message Date
enricobuehler a4210024dc ci(android): canary also feeds Play closed testing (alpha)
android / android (pull_request) Successful in 7m7s
Details
ci / rust (pull_request) Successful in 7m38s
Details
ci / web (pull_request) Successful in 2m25s
Details
ci / docs-site (pull_request) Successful in 4m18s
Details
ci / bun-nix (pull_request) Successful in 2m40s
Details
ci / rust-arm64 (pull_request) Successful in 2m23s
Details 
Closed testing went dry on 2026-08-01 when tags started publishing
straight to production instead of alpha — its testers have been pinned
to the last pre-access build since. Canaries now assign the same
versionCode to beta (open) AND alpha (closed) via play-upload.py's new
repeatable --also-track flag: both PUTs share one Play edit, so one
commit and one review cover both tracks and they can never disagree
about which canary is current. Tags still go to production only.
 2026-08-14 21:45:34 +02:00
enricobuehler ed935ed31c ci(android): canary ships to Play open testing (beta), not internal 
Main-push canaries now land on the open-testing track: public opt-in
link, no tester-list cap. Trade-off documented in the workflow header:
open testing goes through Google review (hours/days), where internal
was review-free (minutes). android-promote's from_track default follows
the canary to beta.
 2026-08-14 21:39:17 +02:00