Skip to content
Triggered via push September 8, 2024 13:53
Status Failure
Total duration 1m 23s
Artifacts

release.yml

on: push
Release to PyPI
54s
Release to PyPI
Fit to window
Zoom out
Zoom in

Deployment protection rules

Reviewers, timers, and other rules protecting deployments in this run
Event Environments Comment
ogrodnek
approved Sep 8, 2024
release

Annotations

1 error and 1 warning
Release 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:ogrodnek/pyview:environment:release` * `repository`: `ogrodnek/pyview` * `repository_owner`: `ogrodnek` * `repository_owner_id`: `17552` * `job_workflow_ref`: `ogrodnek/pyview/.github/workflows/release.yml@refs/heads/release_automate` * `ref`: `refs/heads/release_automate` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
Release to PyPI
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/