Update CHANGELOG.rst and setup.cfg (#28) #1
pypi-release.yml
on: push
Build and publish library to PyPI
25s
Create PyPI release
21s
Annotations
1 error
|
Create PyPI 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 (Publisher with matching claims was not found)
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:aboutcode-org/purl-validator:environment:pypi-publish`
* `repository`: `aboutcode-org/purl-validator`
* `repository_owner`: `aboutcode-org`
* `repository_owner_id`: `95001295`
* `workflow_ref`: `aboutcode-org/purl-validator/.github/workflows/pypi-release.yml@refs/tags/v0.0.1b1`
* `job_workflow_ref`: `aboutcode-org/purl-validator/.github/workflows/pypi-release.yml@refs/tags/v0.0.1b1`
* `ref`: `refs/tags/v0.0.1b1`
* `environment`: `pypi-publish`
See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
pypi_archives
Expired
|
28 MB |
sha256:f6d28382e7f86fef635604b23ccb175e048706b7ff6dd14f8f3cfd1467fc28d8
|
|