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
… for authentication.
lahirumaramba approved these changes Jan 22, 2024
jonathanedey added a commit that referenced this pull request Feb 13, 2024
…rrectly escape change log body. (#759) * fix: Escape release tag body and change PyPi to use trusted publisher for authentication. * fix typo
Sign up for free to join this conversation on . 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.
PyPi no longer accepts username and password authentication for publishing with 2FA enabled accounts. They have additionally made the change to require 2FA on all accounts starting January 1st 2024:
Switching our release to use PyPi's Trusted Publisher method for authentication.
Escaped change log body to allow it to correctly show in in the release tag body.