Skip to content

v0.1.6

v0.1.6 #14

Triggered via release February 3, 2026 00:39
@cmungallcmungall
published v0.1.6
Status Failure
Total duration 46s
Artifacts 1

pypi-publish.yaml

on: release
Build Python 🐍 distributions πŸ“¦ for publishing
22s
Build Python 🐍 distributions πŸ“¦ for publishing
Build and publish Python 🐍 package πŸ“¦ to PyPI and TestPyPI
16s
Build and publish Python 🐍 package πŸ“¦ to PyPI and TestPyPI
Fit to window
Zoom out
Zoom in

Annotations

1 error
Build and publish Python 🐍 package πŸ“¦ to PyPI and TestPyPI
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:monarch-initiative/dismech:environment:pypi-release` * `repository`: `monarch-initiative/dismech` * `repository_owner`: `monarch-initiative` * `repository_owner_id`: `5161984` * `workflow_ref`: `monarch-initiative/dismech/.github/workflows/pypi-publish.yaml@refs/tags/v0.1.6` * `job_workflow_ref`: `monarch-initiative/dismech/.github/workflows/pypi-publish.yaml@refs/tags/v0.1.6` * `ref`: `refs/tags/v0.1.6` * `environment`: `pypi-release` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.

Artifacts

Produced during runtime
Name Size Digest
distribution-files
16.8 MB
sha256:fdfd73c8b0d9b8a158e3c6d39f906817e43d8563be2f639030250c96a08ad649