Skip to content

Merge pull request #211 from blaylockbk/178-can-i-use-gh-action-pypi-… #1

Merge pull request #211 from blaylockbk/178-can-i-use-gh-action-pypi-…

Merge pull request #211 from blaylockbk/178-can-i-use-gh-action-pypi-… #1

Triggered via push December 15, 2023 05:20
Status Failure
Total duration 55s
Artifacts
Publish release on PyPI
46s
Publish release on PyPI
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 notice
Publish release on 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:blaylockbk/Herbie:environment:release` * `repository`: `blaylockbk/Herbie` * `repository_owner`: `blaylockbk` * `repository_owner_id`: `6249613` * `job_workflow_ref`: `blaylockbk/Herbie/.github/workflows/release_to_pypi.yml@refs/tags/2023.12.0` * `ref`: `refs/tags/2023.12.0`
Publish release on 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