Skip to content

ci: dispatch publish after auto release tags#5

Merged
cafitac merged 1 commit intomainfrom
ci/dispatch-publish-after-auto-release
Apr 29, 2026
Merged

ci: dispatch publish after auto release tags#5
cafitac merged 1 commit intomainfrom
ci/dispatch-publish-after-auto-release

Conversation

@cafitac
Copy link
Copy Markdown
Owner

@cafitac cafitac commented Apr 29, 2026

Summary

  • Fix auto-release so bot-created tags explicitly dispatch the publish workflow.
  • Grant actions: write to the auto-release workflow for gh workflow run.
  • Allow the publish workflow to create the GitHub Release when it is manually dispatched on a v* tag ref.
  • Add regression assertions for the dispatch behavior.

Why

GitHub does not reliably start a second workflow from a tag pushed by a workflow using GITHUB_TOKEN. PR #4 correctly bumped and tagged v0.1.10, but the tag push did not start publish.yml. The durable fix is to dispatch publish.yml explicitly after pushing the tag.

Verification

  • RED: tests/test_release_workflows.py failed because auto-release lacked actions: write/gh workflow run, and publish lacked tag-ref workflow_dispatch GitHub Release support.
  • uv run pytest tests/test_release_workflows.py tests/test_bump_release_version.py tests/test_release_metadata.py -q -> 6 passed
  • uv run pytest tests/ -q -> 119 passed
  • uv run python scripts/check_release_metadata.py -> metadata synced at 0.1.10

@cafitac cafitac merged commit d7595df into main Apr 29, 2026
2 checks passed
@cafitac cafitac deleted the ci/dispatch-publish-after-auto-release branch April 29, 2026 21:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant