ci: drop 'released' from release-workflow triggers#2
Merged
Conversation
`gh release create` (the normal release path) emits both `published` and `released` events, so listening to both fires the build-and-upload job twice. Both runs upload with --clobber, but it's wasted CI time. Drop `released`; rely on `published` plus the existing `workflow_dispatch` recovery path documented in the README. Co-Authored-By: Claude Opus 4.7 (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.
Summary
gh release create(the normal release path) emits bothpublishedandreleasedevents, so listening to both — added in ef0c3c8 as a defensive measure — fires the build-and-upload job twice. Both runs upload with--clobberso they're idempotent, but it's wasted CI minutes. Confirmed on the v0.1.8 release: two queued runs, identical artifacts.Drop
released; rely onpublishedplus the existingworkflow_dispatchrecovery path that's already documented under "If the release workflow didn't fire."README updated to remove the now-stale claim that we listen on both event types.
Test plan
publishedis ever missed, confirmgh workflow run release.yml --field tag=vX.Y.Zrecovery still works (already covered in README)🤖 Generated with Claude Code