Skip to content

ci: PyPI release workflow (Trusted Publishing) - #1

Merged
MrPredic merged 1 commit into
mainfrom
ci/pypi-trusted-publishing
Aug 5, 2026
Merged

ci: PyPI release workflow (Trusted Publishing)#1
MrPredic merged 1 commit into
mainfrom
ci/pypi-trusted-publishing

Conversation

@MrPredic

@MrPredic MrPredic commented Aug 5, 2026

Copy link
Copy Markdown
Owner

Package builds clean and passes twine check, but the name is unclaimed on PyPI and there was no release job. Adds a tag-triggered publish over OIDC — no API token stored anywhere.

Needs one manual step before the first tag: add the pending publisher on PyPI (project name, owner MrPredic, workflow release.yml, environment pypi).

The package builds and passes `twine check`, but nothing ever pushed it: the
name is unclaimed on PyPI and the README had to send readers to a git URL.
This adds the tag-triggered release job. It uses OIDC rather than an API
token, so there is no publishing secret in the repo to leak.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VWTgH2xDR5xafCX83YvQQV
@MrPredic
MrPredic merged commit b45e1e7 into main Aug 5, 2026
@MrPredic
MrPredic deleted the ci/pypi-trusted-publishing branch August 5, 2026 14:56
MrPredic added a commit that referenced this pull request Aug 5, 2026
The package builds and passes `twine check`, but nothing ever pushed it: the
name is unclaimed on PyPI and the README had to send readers to a git URL.
This adds the tag-triggered release job. It uses OIDC rather than an API
token, so there is no publishing secret in the repo to leak.


Claude-Session: https://claude.ai/code/session_01VWTgH2xDR5xafCX83YvQQV

Co-authored-by: MrPredic <269417388+MrPredic@users.noreply.github.com>
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
MrPredic added a commit that referenced this pull request Aug 7, 2026
The package builds and passes `twine check`, but nothing ever pushed it: the
name is unclaimed on PyPI and the README had to send readers to a git URL.
This adds the tag-triggered release job. It uses OIDC rather than an API
token, so there is no publishing secret in the repo to leak.
Co-authored-by: MrPredic <269417388+MrPredic@users.noreply.github.com>
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
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