ci(release): release-candidate path via -rc prerelease tags#49
Merged
Conversation
Push a tag with a `-rc` suffix (e.g. v26.06.01-rc.1) to build the real signed APK and publish it as a GitHub pre-release. Pre-releases are not marked "Latest", so the in-app update check (which reads /releases/latest) never offers an RC to users. This lets us test submitted code and feature builds without bumping the announced version. Co-Authored-By: Claude Opus 4.8 (1M context) <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.
What
Adds an optional release-candidate build path so we can build a real signed APK for testing without bumping the version announced to users.
How it works
Push a tag with a
-rcsuffix (e.g.v26.06.01-rc.1). The existingrelease.ymlruns unchanged (assemble, sign, verify, checksum), but the publish step now sets:A
-rctag publishes a pre-release, which GitHub never marks as "Latest". The in-app update check reads/releases/latest, which excludes pre-releases — so an RC is never offered to users. Normal releases (via release-please) are unaffected.No new secrets, jobs, or version bumps. Documented under "Release candidates" in CONTRIBUTING.
🤖 Generated with Claude Code