Set PyPI release environment#6
Merged
Merged
Conversation
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.
This updates the
publishjob in the Python release workflow to run under thepypiGitHub environment. PyPI trusted publishing is currently configured withEnvironment name: pypi, so the release workflow must emit the matching OIDC environment claim for publisher matching to succeed.The failed
v0.1.0b1release already proved that wheel build and smoke validation pass; the only blocker was the trusted publishing claim mismatch. After this merges, configure the pending publisher forpylance-cuvs-cu12as well, then rerun release from a ref that includes this workflow change.