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:strollby/graphene-mongo:ref:refs/tags/v0.4.4.beta.2` * `repository`: `strollby/graphene-mongo` * `repository_owner`: `strollby` * `repository_owner_id`: `75877819` * `workflow_ref`: `strollby/graphene-mongo/.github/workflows/publish.yml@refs/tags/v0.4.4.beta.2` * `job_workflow_ref`: `strollby/graphene-mongo/.github/workflows/publish.yml@refs/tags/v0.4.4.beta.2` * `ref`: `refs/tags/v0.4.4.beta.2` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636