Skip to content

moving to a new method for automatic pypi distribution #1

moving to a new method for automatic pypi distribution

moving to a new method for automatic pypi distribution #1

Triggered via push November 12, 2023 17:33
Status Failure
Total duration 51s
Artifacts 1
Build distribution πŸ“¦
18s
Build distribution πŸ“¦
Publish Python 🐍 distribution πŸ“¦ to PyPI
0s
Publish Python 🐍 distribution πŸ“¦ to PyPI
Sign the Python 🐍 distribution πŸ“¦ with Sigstore and upload them to GitHub Release
0s
Sign the Python 🐍 distribution πŸ“¦ with Sigstore and upload them to GitHub Release
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 notice
Publish Python 🐍 distribution πŸ“¦ to 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 (All lookup strategies exhausted) 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:csteinmetz1/dasp-pytorch:environment:testpypi` * `repository`: `csteinmetz1/dasp-pytorch` * `repository_owner`: `csteinmetz1` * `repository_owner_id`: `16929610` * `job_workflow_ref`: `csteinmetz1/dasp-pytorch/.github/workflows/publish-to-pypi.yml@refs/heads/main` * `ref`: `refs/heads/main`
Publish Python 🐍 distribution πŸ“¦ to TestPyPI
Attempting to perform trusted publishing exchange to retrieve a temporary short-lived API token for authentication against https://test.pypi.org/legacy/ due to __token__ username with no supplied password field

Artifacts

Produced during runtime
Name Size
python-package-distributions Expired
37.3 KB