Skip to content

PyQUDA publish

PyQUDA publish #9

Manually triggered November 4, 2024 06:07
Status Failure
Total duration 50s
Artifacts

PyQUDA.yaml

on: workflow_dispatch
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
pypi-publish
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:CLQCD/PyQUDA:environment:pypi` * `repository`: `CLQCD/PyQUDA` * `repository_owner`: `CLQCD` * `repository_owner_id`: `5997656` * `job_workflow_ref`: `CLQCD/PyQUDA/.github/workflows/PyQUDA.yaml@refs/heads/master` * `ref`: `refs/heads/master` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
pypi-publish
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, softprops/action-gh-release@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/