Skip to content
Triggered via release November 21, 2024 13:03
Status Failure
Total duration 1m 8s
Artifacts 1

publish.yml

on: release
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 2 warnings
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:coti-io/coti-contracts-examples:environment:python-release-env` * `repository`: `coti-io/coti-contracts-examples` * `repository_owner`: `coti-io` * `repository_owner_id`: `37809816` * `job_workflow_ref`: `coti-io/coti-contracts-examples/.github/workflows/publish.yml@refs/tags/1.0.1` * `ref`: `refs/tags/1.0.1` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
npm-publish
Process completed with exit code 1.
build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
npm-publish
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
release-dists
2.11 MB