ci: add PyPI trusted publishing workflow#7
Merged
Conversation
Add a tokenless PyPI publish workflow using GitHub OIDC and pypa/gh-action-pypi-publish. The workflow builds distributions on release publication or manual dispatch and requires the PyPI trusted publisher mapping for the pypi environment. Implemented with assistance from Codex.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
pypa/gh-action-pypi-publish@release/v1.pypiandid-token: write; no PyPI token or secret is added.Verification
sed -n '1,140p' .github/workflows/pypi-publish.yml-> workflow reviewedgit diff --checkandgit diff --cached --check-> clean.venv/bin/python -m pytest -q-> 536 passedRequired PyPI setup before running publish
Configure PyPI Trusted Publisher for project
lurkrwith:agentveil-protocollurkrpypi-publish.ymlpypiAfter the mapping exists, run the
pypi-publishworkflow manually frommainto publish the already-prepared0.4.0package. Future releases can publish by creating/publishing the GitHub release after this workflow is onmain.Implemented with assistance from Codex.