Skip to content

Use a PAT to create the release, not the default GITHUB_TOKEN - #24

Merged
aersam merged 2 commits into
mainfrom
auto-release
Sep 7, 2026
Merged

Use a PAT to create the release, not the default GITHUB_TOKEN#24
aersam merged 2 commits into
mainfrom
auto-release

Conversation

@aersam

@aersam aersam commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

No description provided.

aersam and others added 2 commits September 7, 2026 17:25
Adds .github/workflows/auto-release.yml: after the Python Test
workflow succeeds for a push to main, it reads the version from
pyproject.toml and, if that version hasn't been released yet, creates
a `vX.Y.Z` tag and GitHub Release for that commit. Publishing a
Release is exactly what python-publish.yml already listens for, so
merging a PR that bumps the version now publishes to PyPI with no
separate manual "cut a release" step.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FPDh1XcpTJT48Tw27fD7Ms
GitHub Actions doesn't fire other workflows' triggers (release:
published included) for events performed with the automatic
GITHUB_TOKEN, to prevent recursive workflow runs. Without this fix,
auto-release.yml would successfully tag and "release" a version but
python-publish.yml would silently never run, so nothing would
actually reach PyPI. Switches the release-creation step to a
RELEASE_TOKEN repo secret (a PAT), with a clear failure if it isn't
set, and documents the one-time setup in the README.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FPDh1XcpTJT48Tw27fD7Ms
@aersam
aersam merged commit c98145d 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