ci(release): auto-create GitHub Release on tag push#46
Merged
Conversation
Add create-release job that runs before build jobs. Uses gh release view/create with --generate-notes for idempotency. Removes manual release creation step from release 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.
Problem
Current release workflow requires the GitHub Release to be manually created before the workflow runs, because both build jobs only perform
gh release upload. This creates friction and risk of failed uploads if the release doesn't exist.Solution
Add a dedicated
create-releasejob that:ubuntu-latestbefore both build jobsgh release view--generate-notesif missingbuild-windowsandbuild-linuxnowneeds: create-releaseto avoid upload racesResult
Pushing a version tag (e.g.
v0.21.0) now fully automates the entire release pipeline:Zero manual intervention required.