Implement automatic release drafting #44
Merged
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.
Should allow us to make better use of the moonraker update channel.
Currently only maintains one draft, as
release-drafter
does not seem to be able to differentiate.I will look into adding that functionality in their application, but this should at least help us get started.
With this change we can ask our users to set
channel: beta
and it should automatically use the tag of the newest published release.To target the users on
channel: stable
we would have to mark a release as not pre-release and "latest".channel: dev
will, as now, pull latest commit from master - we should move the general users away from this.Example: https://github.com/Jomik/release-drafter-test/releases