Skip to content

API: Add cross-linking to common-api and prepare for the release (#122) #204

API: Add cross-linking to common-api and prepare for the release (#122)

API: Add cross-linking to common-api and prepare for the release (#122) #204

Triggered via push October 16, 2023 11:41
Status Failure
Total duration 17m 20s
Artifacts 1

ci.yaml

on: push
Matrix: Test with nox
Build distribution packages
27s
Build distribution packages
Test documentation website generation
0s
Test documentation website generation
Publish documentation website to GitHub pages
29s
Publish documentation website to GitHub pages
Create GitHub release
5s
Create GitHub release
Publish packages to PyPI
27s
Publish packages to PyPI
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 notice
Publish packages 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:llucax/frequenz-repo-config-python:ref:refs/tags/v0.5.2` * `repository`: `llucax/frequenz-repo-config-python` * `repository_owner`: `llucax` * `repository_owner_id`: `1031485` * `job_workflow_ref`: `llucax/frequenz-repo-config-python/.github/workflows/ci.yaml@refs/tags/v0.5.2` * `ref`: `refs/tags/v0.5.2`
Publish packages to PyPI
Attempting to perform trusted publishing exchange to retrieve a temporary short-lived API token for authentication against https://upload.pypi.org/legacy/ due to __token__ username with no supplied password field

Artifacts

Produced during runtime
Name Size
dist-packages Expired
48.2 KB