You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Switch to Trusted Publishing for package upload to PyPI in CI #3391
Trusted publishing (with attestations) is currently suggested as good practice to ensure confidence that what users download from PyPI is the same artifact that was generated in GitHub CI, meaning that what I see in GitHub is the same as what is installed - handy for auditing. It also avoids the presence of PyPI tokens as 'secrets' in the CI, which can be exfiltrated by bad actors.
Following the recent litellm supply chain attack this week, I would like to express my support for this*. The docker package is one of 16 packages in the top 500 PyPI packages (by downloads) which use the pypa/gh-action-pypi-publish action but have not yet upgraded it to use Trusted Publishing: this is 'low hanging fruit' in terms of making Python a more secure programming environment.
Instead of using the stored secret token, GitHub vouches for the upload, and PyPI checks the uploading CI workflow filename against a pre-declared filename you set ahead of time (in docker's case the filename is release.yml). It also requires creating an 'environment' for the repo on GitHub (suggested name "pypi") which you also register the package with on PyPI.
I'd like to contribute to this issue by helping migrate the PyPI release workflow to Trusted Publishing using GitHub Actions OIDC.
I'm a DevOps engineer with experience in GitHub Actions, CI/CD pipelines, Docker, and cloud infrastructure, and I'd be glad to help improve the security of the project's release process.
I'll review the existing release.yml workflow and the contribution guidelines before preparing a focused PR. I understand that configuring Trusted Publishing may require maintainer access, and I'm happy to coordinate on that.
Activity
singhharsh77 commentedon Oct 10, 2026
Hi @lmmx,
I'd like to contribute to this issue by helping migrate the PyPI release workflow to Trusted Publishing using GitHub Actions OIDC.
I'm a DevOps engineer with experience in GitHub Actions, CI/CD pipelines, Docker, and cloud infrastructure, and I'd be glad to help improve the security of the project's release process.
I'll review the existing
release.ymlworkflow and the contribution guidelines before preparing a focused PR. I understand that configuring Trusted Publishing may require maintainer access, and I'm happy to coordinate on that.Would you be open to me working on this?
Thanks!