Skip to content

Fix auto-release: call the publish job directly instead of a PAT - #25

Merged
aersam merged 1 commit into
mainfrom
fix-auto-release-no-pat
Sep 7, 2026
Merged

Fix auto-release: call the publish job directly instead of a PAT#25
aersam merged 1 commit into
mainfrom
fix-auto-release-no-pat

Conversation

@aersam

@aersam aersam commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

No description provided.

The just-merged auto-release.yml relied on gh release create
triggering python-publish.yml's release: published listener, using a
RELEASE_TOKEN PAT secret to work around GitHub Actions not letting the
default GITHUB_TOKEN fire other workflows. That secret was never
configured, so the first real run (for 0.4.0) failed cleanly at the
release-creation step with no PyPI publish.

Simpler fix: python-publish.yml gains a workflow_call trigger, and
auto-release.yml calls its deploy job directly instead of going
through a second, separately-triggered workflow run. Since it's all
one run, there's nothing to "trigger" and thus no GITHUB_TOKEN
restriction to work around -- no PAT/secret needed at all.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FPDh1XcpTJT48Tw27fD7Ms
@aersam
aersam merged commit d8fd1c0 into main Sep 7, 2026
2 checks passed
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