[Release 3.7.1]: fix publishing to PyPI by using trusted publisher #228
Conversation
This file contains 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
heerener
force-pushed
the
pypi-changes
branch
2 times, most recently
from
758918f to
35cd7b2
Compare
heerener
force-pushed
the
pypi-changes
branch
from
35cd7b2 to
1d546e5
Compare
heerener
approved these changes
Dec 6, 2024
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.
Context
When publish release 3.7.0 to PyPI, we got the error
Username/Password authentication is no longer supported. Migrate to API Tokens or Trusted Publishers instead. This PR migrates to trusted publishers.Scope
Review