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

2026-08-14T19:47:55Z

enricobuehler commented

2026-08-14 19:47:55 +00:00

Main-push canaries previously went to Play internal; tags to production. Two changes:

Canary → open testing (beta). Public opt-in via https://play.google.com/apps/testing/io.unom.punktfunk, no 100-tester email-list cap. The trade-off is documented in the workflow header: open testing passes Google review (hours–days) where internal was review-free (minutes) — the win is reach, not speed.
Canary → closed testing (alpha) as well. Closed testing has been dry since 2026-08-01: production access let tags skip alpha, stranding its testers on the last pre-access build. play-upload.py gains a repeatable --also-track flag; the extra track PUT shares the upload's Play edit, so one commit and one review cover both tracks and they can never disagree about which canary is current. An --also-track duplicating --track/--promote-from is refused (the second PUT would silently win).

Also: android-promote.yml's from_track default follows the canary from alpha to beta, and the Android README now carries the public opt-in link.

Before the first canary lands: the open-testing track needs one-time Play Console setup (enable + pick countries). Closed testers resume updating automatically; the old internal email list stops receiving canaries and should join via the public link.

Main-push canaries previously went to Play `internal`; tags to `production`. Two changes: 1. **Canary → open testing (`beta`).** Public opt-in via https://play.google.com/apps/testing/io.unom.punktfunk, no 100-tester email-list cap. The trade-off is documented in the workflow header: open testing passes Google review (hours–days) where internal was review-free (minutes) — the win is reach, not speed. 2. **Canary → closed testing (`alpha`) as well.** Closed testing has been dry since 2026-08-01: production access let tags skip `alpha`, stranding its testers on the last pre-access build. `play-upload.py` gains a repeatable `--also-track` flag; the extra track PUT shares the upload's Play edit, so one commit and one review cover both tracks and they can never disagree about which canary is current. An `--also-track` duplicating `--track`/`--promote-from` is refused (the second PUT would silently win). Also: `android-promote.yml`'s `from_track` default follows the canary from `alpha` to `beta`, and the Android README now carries the public opt-in link. Before the first canary lands: the open-testing track needs one-time Play Console setup (enable + pick countries). Closed testers resume updating automatically; the old internal email list stops receiving canaries and should join via the public link.

enricobuehler added 2 commits 2026-08-14 19:47:56 +00:00

ci(android): canary ships to Play open testing (beta), not internal ed935ed31c

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.

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

a4210024dc

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.

enricobuehler merged commit 36e133ae66 into main

2026-08-14 19:50:44 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: unom/punktfunk#234