ci: support manual prereleases built from fork PRs#206
Merged
debba merged 3 commits intoMay 25, 2026
Conversation
Adds workflow_dispatch inputs (pr_number, tag_name, prerelease) to the release workflow so a maintainer can build a prerelease directly from a fork PR without merging or pushing the branch upstream. When pr_number is set, checkout uses refs/pull/<N>/head; the dispatcher controls the tag and prerelease flag. Tag names containing a "-" (semver pre-release qualifier) auto-flag the release as prerelease even without the explicit input. AUR, Snap, and Winget downstream workflows now skip when github.event.release.prerelease is true, so beta channels stay out of the system package managers.
saurabh500
reviewed
May 21, 2026
| prerelease: | ||
| description: "Mark as prerelease (skips AUR/Snap/Winget downstream)." | ||
| type: boolean | ||
| default: false |
Contributor
There was a problem hiding this comment.
Should we assume that forks will always be pre-release and not provide the option to toggle. This would make sure that the release bits are created from main source and not the fork.
Contributor
Author
There was a problem hiding this comment.
yes i think it is better
Contributor
Author
There was a problem hiding this comment.
Implemented in 40c060c — removed the prerelease workflow input entirely and hard-coded prerelease=true on the pr_number branch. Fork PR builds can never be promoted to a full release anymore. Tag-name SemVer auto-detection still applies for tag-triggered / main-built dispatches.
Per @saurabh500's review: when pr_number is set, the build comes from refs/pull/<N>/head (a fork) rather than main, so it must never be promoted to a full release. Removed the prerelease workflow input entirely and hard-code prerelease=true on the pr_number branch. Tag-name SemVer auto-detection still applies for tag-triggered / main-built dispatches.
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (4 files)
Reviewed by kimi-k2.6 · 86,253 tokens |
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
3 participants
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.
Adds workflow_dispatch inputs (pr_number, tag_name, prerelease) to the release workflow so a maintainer can build a prerelease directly from a fork PR without merging or pushing the branch upstream. When pr_number is set, checkout uses refs/pull//head; the dispatcher controls the tag and prerelease flag.
Tag names containing a "-" (semver pre-release qualifier) auto-flag the release as prerelease even without the explicit input. AUR, Snap, and Winget downstream workflows now skip when github.event.release.prerelease is true, so beta channels stay out of the system package managers.