Trusted publishing exchange failure: Token request failed: the server refused the request for the following reasons: * `invalid-publisher`: valid token, but no corresponding publisher (Publisher with matching claims was not found) 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:mglbleta/ca-biositing:environment:testpypi` * `repository`: `mglbleta/ca-biositing` * `repository_owner`: `mglbleta` * `repository_owner_id`: `215086643` * `workflow_ref`: `mglbleta/ca-biositing/.github/workflows/cd.yml@refs/heads/main` * `job_workflow_ref`: `mglbleta/ca-biositing/.github/workflows/cd.yml@refs/heads/main` * `ref`: `refs/heads/main` * `environment`: `testpypi` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.

Trusted publishing exchange failure: Token request failed: the server refused the request for the following reasons: * `invalid-publisher`: valid token, but no corresponding publisher (Publisher with matching claims was not found) 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:mglbleta/ca-biositing:environment:testpypi` * `repository`: `mglbleta/ca-biositing` * `repository_owner`: `mglbleta` * `repository_owner_id`: `215086643` * `workflow_ref`: `mglbleta/ca-biositing/.github/workflows/cd.yml@refs/heads/main` * `job_workflow_ref`: `mglbleta/ca-biositing/.github/workflows/cd.yml@refs/heads/main` * `ref`: `refs/heads/main` * `environment`: `testpypi` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.

Trusted publishing exchange failure: Token request failed: the server refused the request for the following reasons: * `invalid-publisher`: valid token, but no corresponding publisher (Publisher with matching claims was not found) 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:mglbleta/ca-biositing:environment:testpypi` * `repository`: `mglbleta/ca-biositing` * `repository_owner`: `mglbleta` * `repository_owner_id`: `215086643` * `workflow_ref`: `mglbleta/ca-biositing/.github/workflows/cd.yml@refs/heads/main` * `job_workflow_ref`: `mglbleta/ca-biositing/.github/workflows/cd.yml@refs/heads/main` * `ref`: `refs/heads/main` * `environment`: `testpypi` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/