Release experimentals as pre-releases on GitHub #2242
Merged
Conversation
This file contains 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.
Summary
SUMMARY: Build "Release experimentals as pre-releases on GitHub"
Purpose of change
Fixes #2231
Describe the solution
Mark new experimental releases as pre-releases.
Also made manual release actions produce draft releases, so they could be reviewed before going public.
Existing releases would still remain as pre-releases, but they can be marked as pre- en masse with a python script.
Describe alternatives you've considered
Switching over to the newer version of the action (https://github.com/softprops/action-gh-release) and enabling a bunch of new features (changelog autogeneration, new discussion per release).
Testing
Tried this on my fork, works as expected.