ci: Add automated release workflow #1449
Draft
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
This is a first draft (with an absolutely horrendous implementation) of automating our release steps after a PR with a `release/*` label has been merged to the `release` branch. Outstanding TODOs: - I 100% need to implement this with some proper file templating and double check all if-conditions. This is a garbled mess (but probably somehow functional ...) - add the actual release tagging to this as well - document the new release process
ZenBre4ker
reviewed
Mar 4, 2024
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.
This is a first draft (with an absolutely horrendous implementation) of automating our release steps after a PR with a
release/*label has been merged to thereleasebranch.Outstanding TODOs:
I 100% need to implement this with some proper file templating and double check all if-conditions. This is a garbled mess (but probably somehow functional ...)
add the actual release tagging to this as well
document the new release process
This is a highly WIP PR and mostly intended to get some more eyes on this.