Fix PyPI publish workflow with token authentication #7
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
Replace trusted publishing with API token authentication for simpler setup. Also bump version to 0.1.4 for testing the workflow. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
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
uv publish --tokeninstead ofpypa/gh-action-pypi-publishactionProblem
The previous workflow used trusted publishing which requires complex setup on PyPI. This caused authentication failures with error:
invalid-publisher: valid token, but no corresponding publisher.Solution
Switch to the simpler API token approach (same as the copcon project) which only requires setting the
PYPI_API_TOKENsecret in GitHub.Test plan
PYPI_API_TOKENsecret is set in GitHub repository settings🤖 Generated with Claude Code