Skip to content

chore: Add uv.lock (#37) #3

chore: Add uv.lock (#37)

chore: Add uv.lock (#37) #3

Triggered via push April 10, 2025 12:28
Status Failure
Total duration 1m 43s
Artifacts

pre_release.yaml

on: push
Prepare release metadata
11s
Prepare release metadata
Matrix: Run code checks / Lint check / Lint check
Matrix: Run code checks / Type check / Type check
Matrix: Run code checks / Unit tests / Unit tests
Update changelog  /  bump_and_update_changelog
13s
Update changelog / bump_and_update_changelog
Fit to window
Zoom out
Zoom in

Annotations

1 error
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/apify-shared-python:environment:pypi` * `repository`: `apify/apify-shared-python` * `repository_owner`: `apify` * `repository_owner_id`: `24586296` * `workflow_ref`: `apify/apify-shared-python/.github/workflows/pre_release.yaml@refs/heads/master` * `job_workflow_ref`: `apify/apify-shared-python/.github/workflows/pre_release.yaml@refs/heads/master` * `ref`: `refs/heads/master` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.