Skip to content
Triggered via release December 26, 2023 11:22
@jpivarskijpivarski
published 628d030
Status Failure
Total duration 1m 9s
Artifacts 3

cd.yml

on: release
Distribution build
37s
Distribution build
Publish to PyPI
16s
Publish to PyPI
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 notice
Publish 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 (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:jpivarski/ragged:environment:pypi` * `repository`: `jpivarski/ragged` * `repository_owner`: `jpivarski` * `repository_owner_id`: `1852447` * `job_workflow_ref`: `jpivarski/ragged/.github/workflows/cd.yml@refs/tags/v0.0.1` * `ref`: `refs/tags/v0.0.1`
Publish to PyPI
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
Package Metadata Expired
1.92 KB
Packages Expired
14 KB
PyPI README Expired
596 Bytes