ci: add the beta release workflow to main - #84
Merged
Merged
Conversation
GitHub only shows the "Run workflow" button for a workflow_dispatch when the file exists on the default branch. Shipping beta.yml alone lets us publish a beta from any branch — pick the ref at dispatch time and GitHub uses that branch's workflow definition and code. No app change here on purpose: the beta OTA channel itself lives in beta-OTA and stays untested until a beta built from that branch is validated. Co-Authored-By: Claude Opus 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.
GitHub only shows the "Run workflow" button for a workflow_dispatch when the file exists on the default branch. Shipping beta.yml alone lets us publish a beta from any branch — pick the ref at dispatch time and GitHub uses that branch's workflow definition and code.
No app change here on purpose: the beta OTA channel itself lives in beta-OTA and stays untested until a beta built from that branch is validated.