Skip to content

Upload coverage from the test job instead of a dedicated job (#188) #415

Upload coverage from the test job instead of a dedicated job (#188)

Upload coverage from the test job instead of a dedicated job (#188) #415

Re-run triggered July 4, 2026 06:14
Status Failure
Total duration 3m 22s
Artifacts 1

cicd.yaml

on: push
Pre-Commit  /  Pre-Commit
14s
Pre-Commit / Pre-Commit
Matrix: CodeQL / Analyze
Matrix: Build
Matrix: Test
Build-Doc  /  Build
42s
Build-Doc / Build
Upload the current release to PyPI  /  Publish Python distribution to PyPI
Upload the current release to PyPI / Publish Python distribution to PyPI
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
Upload current version to Test PyPI / Publish Python distribution 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:btschwertfeger/python-cmethods:environment:testpypi` * `repository`: `btschwertfeger/python-cmethods` * `repository_owner`: `btschwertfeger` * `repository_owner_id`: `51495182` * `workflow_ref`: `btschwertfeger/python-cmethods/.github/workflows/cicd.yaml@refs/heads/master` * `job_workflow_ref`: `btschwertfeger/python-cmethods/.github/workflows/_pypi_test_publish.yaml@refs/heads/master` * `ref`: `refs/heads/master` * `environment`: `testpypi` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
Upload current version to Test PyPI / Publish Python distribution 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: btschwertfeger/python-cmethods/.github/workflows/_pypi_test_publish.yaml@refs/heads/master Whereas its parent workflow is: btschwertfeger/python-cmethods/.github/workflows/cicd.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