Repository navigation
feat!: route releases by the pre-release checkbox only - #11
Merged
Merged
Conversation
A pre-release goes to Google Play open testing, the public TestFlight beta and Pages /beta/; a release goes to production. The tag only gives the version and build number; its label is free text. Closed and internal tests are no longer automated (play-alpha-track is gone, manual runs take production or the open testing track). GitHub sends "released" both for a new release and for a promoted pre-release; the run promotes when the release already has a beta's App Bundle and builds otherwise. The "published" run of a release skips. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The pre-release checkbox now picks the target; the tag name doesn't.
play-beta-track)/beta/X.Y.Z[-<label>N]), but the label is free text: no more "unknown label", "pre-release needs a pre-release tag" or "is a pre-release tag" errors. The build-number clash check between pre-releases of one version stays.releasedfor a new release and for a promoted pre-release. Thereleasedrun promotes when the release already has a beta's App Bundle (under the tag's name or the renamed one) and builds otherwise; thepublishedrun of a release now skips.play-alpha-track, the "Private beta" TestFlight group and the internal channel. Manual runs takeproductionor the open testing track only; other tracks are published by hand in the store consoles./beta/whatever its tag.Breaking: callers passing
play-alpha-trackmust drop it; dispatch options other thanbeta/productionnow fail.Tested:
mise run lintandmise run testpass; the plan step was run locally against 11 scenarios (pre-releases with beta/alpha/no label, a release's published and released events, a beta-labelled tag published as a release, a promotion and its re-run after the rename, a build-number clash, manualalphaandbeta).🤖 Generated with Claude Code