What to check first
Use TestPyPI to inspect owner access and exercise the intended publishing workflow.
KeySigner setups
- Test a PyPI authenticator code →KeySigner on iPhone or Mac with Sign-in codes
KeySigner setup requirements →
Provider availability
Trusted publishing from GitLab. Requires a project hosted on GitLab.com. Check provider requirements →
Provider walkthroughs
- Rehearse publishing to PyPI from GitLabRehearse a test release from a GitLab.com project and verify that TestPyPI trusts the intended pipeline.
- Replace retired credentials for Bitbucket, npm, and PyPIFind out which credentials stopped working, what replaces them, and how to check repository access or package publishing before changing a live workflow.
What it covers
A successful test on TestPyPI does not change the production project's permissions or publishers.
Troubleshooting
Does PyPI reject the CI publisher after it works on TestPyPI?
Check the trusted publisher for the project on the registry the job is targeting. Compare its workflow and environment with the failing run. If the job still uploads with an account password, password-only uploads had stopped working across PyPI by January 1, 2024.
Replace retired credentials for Bitbucket, npm, and PyPI →
Check PyPI status for reports on PyPI on the Python infrastructure status page.
Documentation and support
PyPI documentation
Review trusted publishing on PyPI and TestPyPI
Add a trusted publisher to an existing PyPI project
Set up authenticator codes for PyPI