fix: use PyPI Trusted Publishing instead of a repo-secret API token - #14
Merged
Merged
Conversation
publish-pypi tried password auth via secrets.PYPI_API_TOKEN, which was never actually set as a repo secret (v1.1.0 was published manually instead). With password empty, gh-action-pypi-publish fell back to OIDC trusted publishing, which then failed too since the job had no id-token permission. Switch to Trusted Publishing properly: add `permissions: id-token: write` and drop the password input so the action always uses OIDC. No long-lived token to rotate or leak. Requires a one-time trusted publisher registration on pypi.org (project kshield → Publishing → add YTT-Global/kshield, workflow release.yml) before the next tagged release.
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.
publish-pypi tried password auth via secrets.PYPI_API_TOKEN, which was never actually set as a repo secret (v1.1.0 was published manually instead). With password empty, gh-action-pypi-publish fell back to OIDC trusted publishing, which then failed too since the job had no id-token permission.
Switch to Trusted Publishing properly: add
permissions: id-token: writeand drop the password input so the action always uses OIDC. No long-lived token to rotate or leak. Requires a one-time trusted publisher registration on pypi.org (project kshield → Publishing → add YTT-Global/kshield, workflow release.yml) before the next tagged release.