Publish Dev Build #4
Triggered via workflow run
November 8, 2024 12:06
jennifgcrl
completed
81f6783
Status
Failure
Total duration
41s
Artifacts
1
publish_dev.yaml
on: workflow_run
build-package
10s
publish-dev
13s
Annotations
1 error and 2 warnings
publish-dev
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:jennifgcrl/levanter:ref:refs/heads/main`
* `repository`: `jennifgcrl/levanter`
* `repository_owner`: `jennifgcrl`
* `repository_owner_id`: `110419915`
* `job_workflow_ref`: `jennifgcrl/levanter/.github/workflows/publish_dev.yaml@refs/heads/main`
* `ref`: `refs/heads/main`
See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
|
build-package
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
build-package
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v2. 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 | |
---|---|---|
package
|
539 KB |
|