Skip to content

chore(ci): Align GitHub workflows across Python projects (#1613) #1

chore(ci): Align GitHub workflows across Python projects (#1613)

chore(ci): Align GitHub workflows across Python projects (#1613) #1

Re-run triggered December 15, 2025 16:29
Status Failure
Total duration 49s
Artifacts

on_master.yaml

on: push
Matrix: Code checks / Lint check / Lint check
Matrix: Code checks / Type check / Type check
Matrix: Tests / Unit tests / Unit tests
Code checks  /  Actions lint check
30s
Code checks / Actions lint check
Doc checks  /  ...  /  Docs check
1m 42s
Doc checks / Doc checks / Docs check
Pre-release  /  Prepare release metadata
30s
Pre-release / Prepare release metadata
Pre-release  /  ...  /  bump_and_update_changelog
16s
Pre-release / Update changelog / bump_and_update_changelog
Doc release  /  Doc release
Doc release / Doc release
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
Pre-release / 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/on_master.yaml@refs/heads/master` * `job_workflow_ref`: `apify/crawlee-python/.github/workflows/_release_pre.yaml@refs/heads/master` * `ref`: `refs/heads/master` * `environment`: `pypi` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
Pre-release / Publish to PyPI
Potential workflow misconfiguration: The claims in this token suggest that the calling workflow is a reusable workflow. In particular, this action was initiated by: apify/crawlee-python/.github/workflows/_release_pre.yaml@refs/heads/master Whereas its parent workflow is: apify/crawlee-python/.github/workflows/on_master.yaml@refs/heads/master 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