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
For the next major version (v3), I propose we remove support for PyPI tokens, and only support PyPI Trusted Publishing.
This will mean that release-from-releaser will no longer work unless you configure the project to accept trusted publishing from your fork of jupyter_releaser.
We would drop support for PYPI_TOKEN, PYPI_TOKEN_MAP, and TWINE_USERNAME. Test PyPI also supports trusted publishing, so that part of the instructions would need to be updated.
The text was updated successfully, but these errors were encountered:
Fair, we could keep PYPI_TOKEN and recommend against using it unless using a private repository. We would still want to get rid of TWINE_USERNAME since it should always be __token__, and still get rid of PYPI_TOKEN_MAP.
Description
For the next major version (v3), I propose we remove support for PyPI tokens, and only support PyPI Trusted Publishing.
This will mean that
release-from-releaser
will no longer work unless you configure the project to accept trusted publishing from your fork ofjupyter_releaser
.We would drop support for
PYPI_TOKEN
,PYPI_TOKEN_MAP
, andTWINE_USERNAME
. Test PyPI also supports trusted publishing, so that part of the instructions would need to be updated.The text was updated successfully, but these errors were encountered: