Skip to content

ci: Update pypi actions to work with trusted publishing (#79) #2

ci: Update pypi actions to work with trusted publishing (#79)

ci: Update pypi actions to work with trusted publishing (#79) #2

Triggered via push December 6, 2023 15:33
Status Failure
Total duration 57s
Artifacts
Fit to window
Zoom out
Zoom in

Annotations

1 error, 1 warning, and 1 notice
Build and publish Python 🐍 distributions 📦 to TestPyPI
Trusted publishing exchange failure: Token request failed: the server refused the request for the following reasons: * `invalid-publisher`: valid token, but no corresponding publisher (All lookup strategies exhausted) This generally indicates a trusted publisher configuration error, but could also indicate an internal error on GitHub or PyPI's part. The claims rendered below are **for debugging purposes only**. You should **not** use them to configure a trusted publisher unless they already match your expectations. If a claim is not present in the claim set, then it is rendered as `MISSING`. * `sub`: `repo:django-cms/djangocms-video:environment:pypi` * `repository`: `django-cms/djangocms-video` * `repository_owner`: `django-cms` * `repository_owner_id`: `69975235` * `job_workflow_ref`: `django-cms/djangocms-video/.github/workflows/publish-to-test-pypi.yml@refs/heads/master` * `ref`: `refs/heads/master`
Build and publish Python 🐍 distributions 📦 to TestPyPI
Input 'skip_existing' has been deprecated with message: The inputs have been normalized to use kebab-case. Use `skip-existing` instead.
Build and publish Python 🐍 distributions 📦 to TestPyPI
Attempting to perform trusted publishing exchange to retrieve a temporary short-lived API token for authentication against https://test.pypi.org/legacy/ due to __token__ username with no supplied password field