chore(ci): add workflow_dispatch trigger to publish workflow#25
Merged
Conversation
Lets us re-trigger PyPI publishes manually without creating a new release. Useful for recovery when a release-triggered run fails due to transient issues (PyPI trusted-publisher config, env approval gate, etc.). Per attune-ai CLAUDE.md lesson on the `pypi` env branch-policy pattern: re-trigger via `gh workflow run python-publish.yml --ref <tag>` after fixing config issues, instead of cutting a new release just to retry the upload. Co-Authored-By: Claude Opus 4.7 <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
Adds
workflow_dispatchtrigger topython-publish.ymlso we can re-trigger PyPI publishes manually when a release-triggered run fails for transient reasons (PyPI publisher config drift, env-approval gate timing, network blips, etc.) — without cutting a new release just to retry.Why now
v0.11.1's release-triggered publish failed on 2026-05-09 with
invalid-publisher: no corresponding publisher. After fixing the PyPI trusted-publisher config, the recommended recovery path (per attune-ai's CLAUDE.md lessons) is:That command requires
workflow_dispatchon the workflow — which this PR adds.Test plan
python -c "import yaml; yaml.safe_load(open('...'))"gh workflow run python-publish.yml --ref v0.11.1and verify the run starts🤖 Generated with Claude Code