ci(release): never overwrite a published release asset - #40
Merged
Merged
Conversation
Consumers pin release-asset checksums (formulaid verifies the skill archive's SHA-256), so replacing an asset under an existing tag would break them. Drop --clobber; the upload step now fails if any asset already exists on the release. A manual run still attaches assets an older release is missing. Co-Authored-By: Claude Opus 5.5 (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.
Release assets are now immutable:
release-assets.ymldrops--clobberand fails if an asset already exists on the release. Asked by formulaid, which pins the skill archive's SHA-256; a replaced asset would break its build. Fixes ship as a new version. README's release checklist says so.🤖 Generated with Claude Code