Add a manual trigger to the release workflow - #4
Merged
Conversation
Publishing the v1.2.0 GitHub Release emitted a ReleaseEvent with action=published, but no run was dispatched for release.yml -- the workflow is active and Actions is enabled, so the event simply did not start a run. That leaves no way to publish without recreating the Release, and no way to retry a failed publish at all. Add workflow_dispatch with a required tag input. Both entry points feed the same tag/version guard, so a manual run cannot publish an artifact whose _version.py disagrees with the tag it claims to be. Also pin the checkout to the tag being released rather than letting it default to the branch, which matters now that a run can start from a dispatch. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0114gUUe4CxYr8W8oC95ffmD
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.
Publishing the v1.2.0 GitHub Release emitted a ReleaseEvent with
action=published, but no run was dispatched for release.yml -- the workflow
is active and Actions is enabled, so the event simply did not start a run.
That leaves no way to publish without recreating the Release, and no way to
retry a failed publish at all.
Add workflow_dispatch with a required tag input. Both entry points feed the
same tag/version guard, so a manual run cannot publish an artifact whose
_version.py disagrees with the tag it claims to be.
Also pin the checkout to the tag being released rather than letting it default
to the branch, which matters now that a run can start from a dispatch.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_0114gUUe4CxYr8W8oC95ffmD