Skip to content
Re-run triggered November 3, 2023 09:52
Status Failure
Total duration 41s
Artifacts

pypi.yml

on: release
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 notice
deploy
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:telekom-mms/Automated-Ansible-Role-Documentation:environment:release` * `repository`: `telekom-mms/Automated-Ansible-Role-Documentation` * `repository_owner`: `telekom-mms` * `repository_owner_id`: `129381922` * `job_workflow_ref`: `telekom-mms/Automated-Ansible-Role-Documentation/.github/workflows/pypi.yml@refs/tags/1.0.2` * `ref`: `refs/tags/1.0.2`
deploy
Attempting to perform trusted publishing exchange to retrieve a temporary short-lived API token for authentication against https://upload.pypi.org/legacy/ due to __token__ username with no supplied password field