Skip to content

inngest_encryption

inngest_encryption #51

Triggered via push February 10, 2025 15:51
Status Failure
Total duration 2m 24s
Artifacts
Matrix: itest
Matrix: lint
Matrix: type-check
Matrix: utest
Matrix: publish-pypi
Fit to window
Zoom out
Zoom in

Annotations

1 error
publish-pypi (3.9)
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:inngest/inngest-py:ref:refs/tags/inngest_encryption@0.0.1a0` * `repository`: `inngest/inngest-py` * `repository_owner`: `inngest` * `repository_owner_id`: `78935958` * `workflow_ref`: `inngest/inngest-py/.github/workflows/inngest_encryption.yml@refs/tags/inngest_encryption@0.0.1a0` * `job_workflow_ref`: `inngest/inngest-py/.github/workflows/inngest_encryption.yml@refs/tags/inngest_encryption@0.0.1a0` * `ref`: `refs/tags/inngest_encryption@0.0.1a0` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.