Skip to content

Create a release

Create a release #2

Manually triggered March 10, 2025 07:07
Status Failure
Total duration 27s
Artifacts

release_python.yaml

on: workflow_dispatch
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
Publish to PyPI
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:apify/fingerprint-suite:environment:pypi` * `repository`: `apify/fingerprint-suite` * `repository_owner`: `apify` * `repository_owner_id`: `24586296` * `workflow_ref`: `apify/fingerprint-suite/.github/workflows/release_python.yaml@refs/heads/master` * `job_workflow_ref`: `apify/fingerprint-suite/.github/workflows/release_python.yaml@refs/heads/master` * `ref`: `refs/heads/master` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
Publish to PyPI
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.