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:Labelbox/labelbox-python:environment:publish-lbox-alignerr` * `repository`: `Labelbox/labelbox-python` * `repository_owner`: `Labelbox` * `repository_owner_id`: `33847372` * `workflow_ref`: `Labelbox/labelbox-python/.github/workflows/publish.yml@refs/heads/develop` * `job_workflow_ref`: `Labelbox/labelbox-python/.github/workflows/lbox-publish.yml@refs/heads/develop` * `ref`: `refs/heads/develop` * `environment`: `publish-lbox-alignerr` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.

Input required and not supplied: path

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 27.

The run was canceled by @mrobers1982.

The operation was canceled.

The run was canceled by @mrobers1982.

The run was canceled by @mrobers1982.

Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0/EZyaQAAAACfsUF7AeD1R631QL2FSyqTRE0yRURHRTA0MTQARWRnZQ==

Failed to restore: Cache service responded with 400

Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0/EZyaQAAAADD43md6+4kTIZvcgozjpk8UEFPRURHRTA2MTUARWRnZQ==

Failed to restore: Cache service responded with 400

Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0/kZyaQAAAABuxk9XTkslTJiOcS+EUthnREVOMzAxMDAwMTAxMDI1AEVkZ2U=

Failed to restore: Cache service responded with 400

Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0AUdyaQAAAADmQqaTRkonQLht40xUAkT+UEhMMzBFREdFMDQxOQBFZGdl

Failed to restore: Cache service responded with 400

Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0AEdyaQAAAACUzxhN7dwrTZ3HMBPetWFmUEhYMzFFREdFMDIwOABFZGdl

Failed to restore: Cache service responded with 400

Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0GUdyaQAAAAAusqkQajcuQrJETQwUa2amREVOMzAxMDAwMTA4MDIzAEVkZ2U=

Failed to restore: Cache service responded with 400

Potential workflow misconfiguration: The claims in this token suggest that the calling workflow is a reusable workflow. In particular, this action was initiated by: Labelbox/labelbox-python/.github/workflows/lbox-publish.yml@refs/heads/develop Whereas its parent workflow is: Labelbox/labelbox-python/.github/workflows/publish.yml@refs/heads/develop Reusable workflows are **not currently supported** by PyPI's Trusted Publishing functionality, and are subject to breakage. Users are **strongly encouraged** to avoid using reusable workflows for Trusted Publishing until support becomes official. Please, do not report bugs if this breaks. For more information, see: * https://docs.pypi.org/trusted-publishers/troubleshooting/#reusable-workflows-on-github * https://github.com/pypa/gh-action-pypi-publish/issues/166 — subscribe to this issue to watch the progress and learn when reusable workflows become supported officially