Release workflow creates the release for a pushed tag; add v1.1.0 notes - #2
Merged
Merged
Conversation
Previously the tag-push run only uploaded assets and failed unless the release had been created by hand first. A new job creates the release (notes from docs/release-notes/<tag>.md, else generated) before the Windows and macOS builds upload to it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017ZHKbLKcpoa8QJGzqkbDTJ
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
2 participants
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
Until now, a tag-push run of the release workflow only uploaded build assets, so it failed unless someone had already created the release by hand. This PR adds a
releasejob that creates the GitHub release if it doesn't exist yet. The Windows and macOS build jobs now wait for that job before uploading to the release. After this change, pushing av*tag is all a release takes.docs/release-notes/<tag>.mdwhen that file exists. Otherwise the job uses GitHub's generated notes.docs/release-notes/v1.1.0.mdfor the upcoming v1.1.0 tag.Testing
v1.1.0tag push after this merges.🤖 Generated with Claude Code
https://claude.ai/code/session_017ZHKbLKcpoa8QJGzqkbDTJ
Generated by Claude Code