Skip to content

Git Stream Publish

Git Stream Publish #2

Manually triggered September 2, 2024 16:05
Status Failure
Total duration 4m 56s
Artifacts

publish.yml

on: workflow_dispatch
pre_release  /  pypi-publish
3m 12s
pre_release / pypi-publish
release  /  pypi-publish
1m 4s
release / pypi-publish
Fit to window
Zoom out
Zoom in

Deployment protection rules

Reviewers, timers, and other rules protecting deployments in this run
Event Environments Comment
tardis4500
approved Sep 2, 2024
Staging

Annotations

1 error and 2 warnings
release / 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 (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:tardis4500/git-stream:environment:Production` * `repository`: `tardis4500/git-stream` * `repository_owner`: `tardis4500` * `repository_owner_id`: `6739064` * `job_workflow_ref`: `tardis4500/git-stream/.github/workflows/pypi-publish.yml@refs/heads/main` * `ref`: `refs/heads/main` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
pre_release / pypi-publish
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
release / pypi-publish
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/