ci(release): add alpha/beta/rc release channel#4388
Merged
Conversation
Add a 'channel' dispatch input (none/alpha/beta/rc) wired to the reusable release workflow's preRelease. bump + channel cuts an auto-incrementing pre-release (e.g. major + beta -> 6.0.0-beta.1, 6.0.0-beta.2); channel=none finalises the stable version. Flags pre-release GitHub releases so the latest stable stays "Latest".
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4388 +/- ##
=======================================
Coverage 93.05% 93.05%
=======================================
Files 339 339
Lines 14882 14882
Branches 1567 1567
=======================================
Hits 13848 13848
Misses 770 770
Partials 264 264 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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 kind of change does this PR introduce?
CI — adds a pre-release channel to the Release dispatch.
What is the new behavior?
The Release workflow gains a
channelchoice input (none/alpha/beta/rc, defaultnone), combined with the existingbump(major/minor/patch):major+beta→6.0.0-beta.1; re-run →6.0.0-beta.2(the counter auto-increments from existingv6.0.0-beta.Ntags)rc→6.0.0-rc.1(per-channel counter;beta.10correctly orders abovebeta.9)major+none→ finalises6.0.0(last stable + bump)Versions use dotted SemVer 2.0 pre-release form (
-beta.1), which NuGet orders correctly. Pre-release runs flag the GitHub release with--prerelease, so the latest stable stays "Latest".channel=nonemaps to an emptypreRelease(choice inputs can't be empty); the work is delegated to the reusableworkflow-common-release/workflow-common-create-releaseinreactiveui/actions-common@main.What is the current behavior?
The Release dispatch only exposes
bump(patch/minor/major) and always cuts a stable RTM version (vX.Y.Z). There is no supported way to publish an incrementing alpha/beta/rc pre-release.What might this PR break?
None.
channeldefaults tonone, which reproduces today's stable-release behaviour exactly. Finalising a stable release uses the same "last stable + bump" math as before, so re-select the samebumpthe betas used.Checklist
mainbranchAdditional information
Depends on the reusable-workflow side in
reactiveui/actions-common@main(already merged):pre-release-idoncompute-version-and-tag,preRelease/prereleaseonworkflow-common-release, andprereleaseonworkflow-common-create-release.