Skip to content

Update publish.yml

Update publish.yml #5

Triggered via push October 4, 2024 23:00
Status Failure
Total duration 33s
Artifacts

publish.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

1 error, 1 warning, 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:jito-labs/jito-py-rpc:environment:release` * `repository`: `jito-labs/jito-py-rpc` * `repository_owner`: `jito-labs` * `repository_owner_id`: `87542516` * `job_workflow_ref`: `jito-labs/jito-py-rpc/.github/workflows/publish.yml@refs/heads/master` * `ref`: `refs/heads/master`
deploy
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
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