Run release #1
Triggered via release
July 25, 2024 14:23
jirispilka
published
b8ae10f
Status
Failure
Total duration
1m 50s
Artifacts
–
run_release.yaml
on: release
Matrix: Run code checks / Run linting / Linting
Matrix: Run code checks / Run type checking / Type checking
Matrix: Run code checks / Run unit tests / Unit tests
Check whether to release
0s
Publish to PyPI
/
Publish to PyPI
36s
Annotations
1 error
Publish to PyPI / 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:apify/apify-haystack:environment:pypi`
* `repository`: `apify/apify-haystack`
* `repository_owner`: `apify`
* `repository_owner_id`: `24586296`
* `job_workflow_ref`: `apify/apify-haystack/.github/workflows/_publish_to_pypi.yaml@refs/tags/v0.0.1-alpha`
* `ref`: `refs/tags/v0.0.1-alpha`
See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
|