Skip to content

refactor a bit, introduce setuptools-scm, liniting, preparing to publ… #1

refactor a bit, introduce setuptools-scm, liniting, preparing to publ…

refactor a bit, introduce setuptools-scm, liniting, preparing to publ… #1

Triggered via push November 10, 2024 08:45
Status Failure
Total duration 29s
Artifacts

pypi.yml

on: push
upload release to PyPI
20s
upload release to PyPI
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
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:bornhack/bma-client-python:environment:pypi-publish` * `repository`: `bornhack/bma-client-python` * `repository_owner`: `bornhack` * `repository_owner_id`: `14115098` * `job_workflow_ref`: `bornhack/bma-client-python/.github/workflows/pypi.yml@refs/tags/v0.1.0` * `ref`: `refs/tags/v0.1.0` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
upload release to PyPI
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/