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:Rot127/capstone:ref:refs/tags/v300.0.2` * `repository`: `Rot127/capstone` * `repository_owner`: `Rot127` * `repository_owner_id`: `45763064` * `workflow_ref`: `Rot127/capstone/.github/workflows/python-publish-release.yml@refs/tags/v300.0.2` * `job_workflow_ref`: `Rot127/capstone/.github/workflows/python-publish-release.yml@refs/tags/v300.0.2` * `ref`: `refs/tags/v300.0.2` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.

Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists