Repository navigation
fix: restore PyPI token publish and limit non-main CI - #8
Merged
Merged
Conversation
Trusted Publishing fails because PyPI has no matching OIDC publisher. Restore token auth used by 0.1.x, and run the full test matrix plus the packaging job only on master/main. Co-authored-by: arena-agent <297053741+arena-agent@users.noreply.github.com>
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.
Why
The
v0.2.0publish run failed withinvalid-publisher/Publisher with matching claims was not found. The 0.2.0 workflow switched to Trusted Publishing (OIDC), but this project has never had a matching publisher on PyPI. 0.1.x releases usedsecrets.PYPI_API_TOKEN.Changes
__token__+PYPI_API_TOKENagain (attestations off; they need OIDC).pypienvironment.skip-existing: trueso a re-run ofv0.2.0after a partial upload is safe.master/main. PRs run lint + Python 3.12.master/main.After merge
Re-run the failed
v0.2.0workflow (or push the tag again) so 0.2.0 lands on PyPI. ConfirmPYPI_API_TOKENis still a repo secret.