Skip to content
Triggered via pull request January 31, 2024 09:35
@jamesWalczakjamesWalczak
synchronize #9
feature_5
Status Failure
Total duration 1m 19s
Artifacts

publish_on_testpypi.yaml

on: pull_request
Matrix: Build geolake client and publish to TestPyPI
Fit to window
Zoom out
Zoom in

Annotations

1 error, 1 warning, and 1 notice
Build geolake client and publish to TestPyPI (3.11, ubuntu-latest)
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:CMCC-Foundation/geolake:pull_request` * `repository`: `CMCC-Foundation/geolake` * `repository_owner`: `CMCC-Foundation` * `repository_owner_id`: `26088734` * `job_workflow_ref`: `CMCC-Foundation/geolake/.github/workflows/publish_on_testpypi.yaml@refs/pull/9/merge` * `ref`: `refs/pull/9/merge`
Build geolake client and publish to TestPyPI (3.11, ubuntu-latest)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-python@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Build geolake client and publish to TestPyPI (3.11, ubuntu-latest)
Attempting to perform trusted publishing exchange to retrieve a temporary short-lived API token for authentication against https://test.pypi.org/legacy/ due to __token__ username with no supplied password field