Skip to content

Bump version v2023.10.1004 -> v2023.10.1005 #5

Bump version v2023.10.1004 -> v2023.10.1005

Bump version v2023.10.1004 -> v2023.10.1005 #5

Triggered via push October 29, 2023 12:39
Status Failure
Total duration 1m 14s
Artifacts
upload release to PyPI
1m 4s
upload release to PyPI
Fit to window
Zoom out
Zoom in

Annotations

1 error, 1 warning, and 1 notice
upload release 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:freemocap/ajc27_freemocap_blender_addon:environment:release` * `repository`: `freemocap/ajc27_freemocap_blender_addon` * `repository_owner`: `freemocap` * `repository_owner_id`: `97994512` * `job_workflow_ref`: `freemocap/ajc27_freemocap_blender_addon/.github/workflows/publish_to_pypi_when_new_tag_is_pushed_to_main.yml@refs/tags/v2023.10.1005` * `ref`: `refs/tags/v2023.10.1005`
upload release to PyPI
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
upload release 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