Publish to PyPI #9
ltorres6Annotations
1 error and 2 warnings
|
release
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:OSIPI/osipi:ref:refs/heads/sematic-version`
* `repository`: `OSIPI/osipi`
* `repository_owner`: `OSIPI`
* `repository_owner_id`: `46761096`
* `job_workflow_ref`: `OSIPI/osipi/.github/workflows/release.yaml@refs/heads/sematic-version`
* `ref`: `refs/heads/sematic-version`
See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
|
|
release
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, Gr1N/setup-poetry@v8. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
release
Unexpected input(s) 'username', valid inputs are ['entryPoint', 'args', 'user', 'password', 'repository-url', 'repository_url', 'packages-dir', 'packages_dir', 'verify-metadata', 'verify_metadata', 'skip-existing', 'skip_existing', 'verbose', 'print-hash', 'print_hash', 'attestations']
|