ci: dispatch publish after auto release tags#5
Merged
Conversation
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
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
actions: writeto the auto-release workflow forgh workflow run.v*tag ref.Why
GitHub does not reliably start a second workflow from a tag pushed by a workflow using
GITHUB_TOKEN. PR #4 correctly bumped and taggedv0.1.10, but the tag push did not startpublish.yml. The durable fix is to dispatchpublish.ymlexplicitly after pushing the tag.Verification
tests/test_release_workflows.pyfailed because auto-release lackedactions: write/gh workflow run, and publish lacked tag-refworkflow_dispatchGitHub Release support.uv run pytest tests/test_release_workflows.py tests/test_bump_release_version.py tests/test_release_metadata.py -q->6 passeduv run pytest tests/ -q->119 passeduv run python scripts/check_release_metadata.py-> metadata synced at0.1.10