Merge pull request #32 from hamnis/dependabot/github_actions/actions/… #22
pypi-build-n-publish.yml
on: push
linting
27s
build-and-publish
38s
Annotations
1 error, 1 warning, and 1 notice
build-and-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:jimisola/maven-artifact:ref:refs/heads/main`
* `repository`: `jimisola/maven-artifact`
* `repository_owner`: `jimisola`
* `repository_owner_id`: `1577689`
* `job_workflow_ref`: `jimisola/maven-artifact/.github/workflows/pypi-build-n-publish.yml@refs/heads/main`
* `ref`: `refs/heads/main`
|
build-and-publish
Unexpected input(s) 'sign-artifacts', 'gpg-private-key', 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']
|
build-and-publish
Attempting to perform trusted publishing exchange to retrieve a temporary short-lived API token for authentication against https://test.pypi.org/legacy/ due to __token__ username with no supplied password field
|