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
Given that adding a trusted publisher to an existing PyPI project requires owner level control of the PyPI project, I can't make the necessary changes to enable this, but c.f. the following PRs as examples of what is needed after the fact:
At the moment uproot still uses long lived API token based publishing to PyPI
uproot5/.github/workflows/deploy.yml
Lines 43 to 45 in 734700e
It would be preferable from a security and long term security maintenance view (c.f. scientific-python/summit-2024#9) to use Trusted Publishers for this.
Given that adding a trusted publisher to an existing PyPI project requires owner level control of the PyPI project, I can't make the necessary changes to enable this, but c.f. the following PRs as examples of what is needed after the fact:
The text was updated successfully, but these errors were encountered: