Skip to content

Fix the usage of the pypa/gh-action-pypi-publish action #25

Fix the usage of the pypa/gh-action-pypi-publish action

Fix the usage of the pypa/gh-action-pypi-publish action #25

Triggered via push January 4, 2024 22:30
Status Failure
Total duration 46s
Artifacts

release.yml

on: push
Deploy to PYPI
36s
Deploy to PYPI
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 notice
Deploy to PYPI
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:mivek/python-metar-taf-parser:environment:pypi` * `repository`: `mivek/python-metar-taf-parser` * `repository_owner`: `mivek` * `repository_owner_id`: `9912558` * `job_workflow_ref`: `mivek/python-metar-taf-parser/.github/workflows/release.yml@refs/tags/1.8.1` * `ref`: `refs/tags/1.8.1`
Deploy to PYPI
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