chore: rename publish.yaml to release.yml (match PyPI trusted publisher registration) - #175
Merged
Merged
Conversation
…er registration) The pending trusted publisher on PyPI expects the workflow file to be named 'release.yml'; ours was 'publish.yaml', so the token exchange returned 'invalid-publisher' on the v0.1.1 tag push. Renaming the file so its 'workflow_ref' claim matches the registration. No content change.
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.
The pending trusted publisher on PyPI expects the workflow file to be
named 'release.yml'; ours was 'publish.yaml', so the token exchange
returned 'invalid-publisher' on the v0.1.1 tag push. Renaming the file
so its 'workflow_ref' claim matches the registration. No content change.