Skip to content

publish primerForge to pypi #12

publish primerForge to pypi

publish primerForge to pypi #12

Triggered via release April 18, 2024 17:13
@dr-joe-wirthdr-joe-wirth
released a848e63
Status Failure
Total duration 36s
Artifacts

pypi-release.yml

on: release
upload release to PyPi
27s
upload release to PyPi
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
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:dr-joe-wirth/primerForge:ref:refs/tags/v1.0.0` * `repository`: `dr-joe-wirth/primerForge` * `repository_owner`: `dr-joe-wirth` * `repository_owner_id`: `71667025` * `job_workflow_ref`: `dr-joe-wirth/primerForge/.github/workflows/pypi-release.yml@refs/tags/v1.0.0` * `ref`: `refs/tags/v1.0.0` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
upload release to PyPi
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/setup-python@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
upload release to PyPi
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/