ci: use OIDC trusted publishing via wevm/changelogs#138
Merged
Conversation
e165a90 to
7aa14fa
Compare
wevm/changelogs now natively supports PyPI Trusted Publishing (OIDC) as of tempoxyz/changelogs#116. When pypi-token is empty and the workflow has id-token: write, it mints a short-lived PyPI API token by exchanging the GitHub OIDC ID token at PyPI's _/oidc/mint-token endpoint, removing the need for a long-lived static API token. Pin to the merge commit (de02501) until a new changelogs release is cut, and grant id-token: write + environment: release to the release job so the OIDC mint flow runs and matches the registered Trusted Publisher (tempoxyz/pympp + publish.yml + release).
7aa14fa to
0126559
Compare
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
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.
Problem
Releases since
v0.6.0have been failing with403 Forbiddenfrom PyPI:Root cause:
wevm/changelogsdid not support PyPI Trusted Publishing — it required a staticpypi-tokeninput, which we had not configured.Fix
Two-part fix:
pypi-tokenis empty and the workflow hasid-token: write, it mints a short-lived PyPI API token via PyPI's_/oidc/mint-tokenendpoint and uses it asTWINE_PASSWORDfor the existing twine upload.id-token: write+environment: releaseso the OIDC mint flow runs.