fix(ci): upload release assets to draft before publishing#12
Merged
Conversation
GitHub immutable releases reject asset uploads after publish. Create the release as a draft with assets attached, then flip to published. Also bump actions/checkout v4 -> v5 to run natively on Node 24. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Problem
The Release workflow failed with:
GitHub's immutable releases only allow asset uploads before a release is published.
action-gh-releasewas publishing the release and then uploading assets, which is now rejected.Changes
draft: true) so.app.zip/.dmgupload to the unpublished release, then a follow-up step flips it to published viagh release edit --draft=false.actions/checkout@v4→@v5to run natively on Node 24 (silences the Node 20 deprecation warning).The
macos-latestmigration notice is informational only and left unchanged.Note
The stuck, asset-less
v0.3.0release + tag and the emptyv0.3.1draft were deleted, so re-running the release on a fresh tag is clean.🤖 Generated with Claude Code