ci: automate GitHub Release creation on version tags#28
Merged
Conversation
Releases were previously created manually; this removes that friction and ensures every vX.Y.Z tag gets a corresponding GitHub Release with auto-generated notes from merged PRs and commits. Signed-off-by: Nerijus Bendžiūnas <nerijus.bendziunas@gmail.com>
benner
force-pushed
the
ci/add-release-workflow
branch
from
90c8056 to
b256e08
Compare
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.
Releases were previously created manually; this removes that friction
and ensures every vX.Y.Z tag gets a corresponding GitHub Release with
auto-generated notes from merged PRs and commits.