Skip to content
Triggered via release January 28, 2024 03:25
@cerrussellcerrussell
published 0.1.0
Status Failure
Total duration 57s
Artifacts

release.yml

on: release
Fit to window
Zoom out
Zoom in

Annotations

1 error, 1 warning, and 1 notice
deploy
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:AppThreat/atom-tools:ref:refs/tags/0.1.0` * `repository`: `AppThreat/atom-tools` * `repository_owner`: `AppThreat` * `repository_owner_id`: `58593322` * `job_workflow_ref`: `AppThreat/atom-tools/.github/workflows/release.yml@refs/tags/0.1.0` * `ref`: `refs/tags/0.1.0`
deploy
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-python@v4, softprops/action-gh-release@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
deploy
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