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:eracle@3613943/OpenOutSend@1335159073:environment:pypi` * `repository`: `eracle/OpenOutSend` * `repository_owner`: `eracle` * `repository_owner_id`: `3613943` * `workflow_ref`: `eracle/OpenOutSend/.github/workflows/deploy.yml@refs/heads/main` * `job_workflow_ref`: `eracle/OpenOutSend/.github/workflows/deploy.yml@refs/heads/main` * `ref`: `refs/heads/main` * `environment`: `pypi` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-python@v5, astral-sh/setup-uv@v5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

No file matched to [**/uv.lock,**/requirements*.txt]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.