ci: replace content-delivery-release-bot with token #24
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
For releases to PyPI, migrate away from password-based auth with content-delivery-release-bot to using a token instead. (Tokens were not available at the time content-delivery-release-bot was introduced.) Reasons for doing this include: - the team associated with content-delivery-release-bot doesn't exist any more - tokens are project-scoped, so any accidents which expose this token will not put any other projects at risk & won't require token resets for any other project
lipoja
approved these changes
Jun 22, 2020
chandwanitulsi
approved these changes
Jun 22, 2020
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.
For releases to PyPI, migrate away from password-based auth with
content-delivery-release-bot to using a token instead. (Tokens
were not available at the time content-delivery-release-bot was
introduced.)
Reasons for doing this include:
exist any more
token will not put any other projects at risk & won't require
token resets for any other project