(release): upload release assets per-file with retries - #49
Merged
Conversation
A single whole-batch `gh release create ... dist/*` aborts entirely when uploads.github.com returns an intermittent 401 on one asset (typically a .blockmap), leaving a partial release that needs manual recovery (hit on v0.0.32). Create the draft once (tolerating an existing draft on re-run), then upload each asset individually with up to 5 retries.
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.
Why
The
publishjob uploads all artifacts in one shot (gh release create ... dist/*). An intermittent 401 from uploads.github.com on a single asset (often a .blockmap) aborts the whole command, leaving a partial release — hit on v0.0.32 (1/18 assets).What
publish only runs on tag pushes, so this can't affect PR CI.
Generated with Claude Code