Use the org-level PYPI_USERNAME/PYPI_PASSWORD secrets for publishing#109
Merged
Conversation
The repo-level TWINE_USERNAME/TWINE_PASSWORD secrets get a 403 from PyPI; the PYPI_* names publish successfully from the masonite and orm repositories.
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 v3.0.0.post1 publish failed with
403 Forbiddenfrom PyPI using the repo-levelTWINE_USERNAME/TWINE_PASSWORDsecrets. ThePYPI_USERNAME/PYPI_PASSWORDnames publish successfully from the masonite and orm repositories (org-level secrets). Follow-up to #107.