Open frankinspace opened 1 month ago
I also tried working around this by not using trusted publishing and instead providing a PYPI_TOKEN
env variable to finalize-release
but could not get that to work either. That problem might still be user error though, not sure.
I also tried working around this by not using trusted publishing and instead providing a
PYPI_TOKEN
env variable tofinalize-release
but could not get that to work either.
Interesting. This could have otherwise been a good enough workaround for now (not sure Test PyPI supports the trusted publishers?). What error did you encounter with this approach?
Description
The documentation suggests publishing a release from a fork to Test PyPi first to ensure the process works: https://jupyter-releaser.readthedocs.io/en/latest/how_to_guides/convert_repo_from_repo.html#initial-release-workflow
This is done by setting
TWINE_REPOSITORY_URL: https://test.pypi.org/legacy/
environment variable on thefinalize-release
step in the workflow.However, this fails with the following error:
The reason seems to be because the token url seems to be hard coded to pypi.org: https://github.com/jupyter-server/jupyter_releaser/blob/f477486b16a7297ee8d82ec8add2135885973e44/jupyter_releaser/python.py#L24
Reproduce
TWINE_REPOSITORY_URL: https://test.pypi.org/legacy/
environment variable on thefinalize-release
step in the workflow422 Client Error: Unprocessable Entity for url: https://pypi.org/_/oidc/github/mint-token
Expected behavior
Package is published to test pypi
Context
Troubleshoot Output
Command Line Output
Browser Output