Skip to content

Stable release

Stable release #2

Manually triggered December 16, 2025 08:25
Status Failure
Total duration 2m 21s
Artifacts

manual_release_stable.yaml

on: workflow_dispatch
Matrix: Code checks / Lint check / Lint check
Matrix: Code checks / Type check / Type check
Code checks  /  Actions lint check
30s
Code checks / Actions lint check
Prepare release metadata
24s
Prepare release metadata
Update changelog  /  bump_and_update_changelog
18s
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 (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:apify/crawlee-python:environment:pypi` * `repository`: `apify/crawlee-python` * `repository_owner`: `apify` * `repository_owner_id`: `24586296` * `workflow_ref`: `apify/crawlee-python/.github/workflows/manual_release_stable.yaml@refs/heads/master` * `job_workflow_ref`: `apify/crawlee-python/.github/workflows/manual_release_stable.yaml@refs/heads/master` * `ref`: `refs/heads/master` * `environment`: `pypi` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.