Repository navigation
ci(release): create prerelease releases - #432
Merged
Merged
Conversation
Signed-off-by: lixd <xueduan.li@gmail.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #432 +/- ##
=======================================
Coverage 47.30% 47.30%
=======================================
Files 7 7
Lines 613 613
Branches 176 176
=======================================
Hits 290 290
Misses 250 250
Partials 73 73 ☔ 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
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.
/kind cleanup
What this PR does / why we need it:
Set
prerelease: truefor the Console GitHub release workflow so tag-triggered releases remain prereleases until the release is manually promoted.Which issue(s) this PR fixes:
Fixes #
Special notes for reviewers:
The current release workflow only changes the GitHub Release status; OSS upload paths and release assets are unchanged.
Does this PR introduced a user-facing change?
None
Additional documentation, usage docs, etc.: