Release version 0.2.0 #2
python-publish.yml
on: release
release-build
17s
pypi-publish
9s
Annotations
1 error and 3 warnings
|
pypi-publish
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:4mritGiri/npdatetime:environment:pypi`
* `repository`: `4mritGiri/npdatetime`
* `repository_owner`: `4mritGiri`
* `repository_owner_id`: `85377404`
* `workflow_ref`: `4mritGiri/npdatetime/.github/workflows/python-publish.yml@refs/tags/v0.2.0`
* `job_workflow_ref`: `4mritGiri/npdatetime/.github/workflows/python-publish.yml@refs/tags/v0.2.0`
* `ref`: `refs/tags/v0.2.0`
See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
|
|
release-build
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
pypi-publish
Unexpected input(s) 'token', valid inputs are ['user', 'password', 'repository-url', 'repository_url', 'packages-dir', 'packages_dir', 'verify-metadata', 'verify_metadata', 'skip-existing', 'skip_existing', 'verbose', 'print-hash', 'print_hash', 'attestations']
|
|
pypi-publish
Unexpected input(s) 'token', valid inputs are ['user', 'password', 'repository-url', 'repository_url', 'packages-dir', 'packages_dir', 'verify-metadata', 'verify_metadata', 'skip-existing', 'skip_existing', 'verbose', 'print-hash', 'print_hash', 'attestations']
|