Skip to content

Labelbox Python SDK Publish #160

Labelbox Python SDK Publish

Labelbox Python SDK Publish #160

Re-run triggered October 27, 2025 17:36
Status Failure
Total duration 6m 54s
Artifacts 3

publish.yml

on: workflow_dispatch
build-lbox  /  path-filter
25s
build-lbox / path-filter
Matrix: build-lbox / test-build
Matrix: build-lbox / build
build-lbox  /  ...  /  detect-env
5s
build-lbox / provenance_python / detect-env
Matrix: build-lbox / container-publish
Matrix: build-lbox / pypi-publish
build-lbox  /  ...  /  generator
22s
build-lbox / provenance_python / generator
build-lbox  /  ...  /  upload-assets
10s
build-lbox / provenance_python / upload-assets
build-lbox  /  ...  /  final
4s
build-lbox / provenance_python / final
build
build
provenance_python  /  detect-env
provenance_python / detect-env
Matrix: test-build
publish-python-package-to-release
publish-python-package-to-release
provenance_python  /  upload-assets
provenance_python / upload-assets
provenance_container  /  detect-env
provenance_container / detect-env
provenance_python  /  final
provenance_python / final
provenance_container  /  generator
provenance_container / generator
provenance_container  /  final
provenance_container / final
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
build-lbox / pypi-publish (lbox-alignerr)
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:Labelbox/labelbox-python:environment:publish-lbox-alignerr` * `repository`: `Labelbox/labelbox-python` * `repository_owner`: `Labelbox` * `repository_owner_id`: `33847372` * `workflow_ref`: `Labelbox/labelbox-python/.github/workflows/publish.yml@refs/heads/develop` * `job_workflow_ref`: `Labelbox/labelbox-python/.github/workflows/lbox-publish.yml@refs/heads/develop` * `ref`: `refs/heads/develop` * `environment`: `publish-lbox-alignerr` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
pypi-publish
Unable to download artifact(s): Artifact not found for name: build Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact. For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
build-lbox / pypi-publish (lbox-alignerr)
Potential workflow misconfiguration: The claims in this token suggest that the calling workflow is a reusable workflow. In particular, this action was initiated by: Labelbox/labelbox-python/.github/workflows/lbox-publish.yml@refs/heads/develop Whereas its parent workflow is: Labelbox/labelbox-python/.github/workflows/publish.yml@refs/heads/develop 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