Skip to content

Initial release to PyPI #4

Initial release to PyPI

Initial release to PyPI #4

Triggered via release February 23, 2026 14:58
@p1-mmrp1-mmr
published 1.0.0
Status Failure
Total duration 33s
Artifacts 1

python-publish.yml

on: release
release-build
17s
release-build
pypi-publish
10s
pypi-publish
Fit to window
Zoom out
Zoom in

Annotations

1 error
pypi-publish
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:P1sec/MCC_MNC:ref:refs/tags/1.0.0` * `repository`: `P1sec/MCC_MNC` * `repository_owner`: `P1sec` * `repository_owner_id`: `856786` * `workflow_ref`: `P1sec/MCC_MNC/.github/workflows/python-publish.yml@refs/tags/1.0.0` * `job_workflow_ref`: `P1sec/MCC_MNC/.github/workflows/python-publish.yml@refs/tags/1.0.0` * `ref`: `refs/tags/1.0.0` * `environment`: `MISSING` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.

Artifacts

Produced during runtime
Name Size Digest
release-dists Expired
1.29 MB
sha256:385f58ba5a9a9e06847d510373a737126bb7c7d2ba8160f3caeae67a7c8508f8