0.2.1 #633
cd.yml
on: release
Distribution build
20s
Publish to PyPI
23s
Annotations
1 error
|
Publish 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 (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:Parcels-code/virtualship:environment:pypi`
* `repository`: `Parcels-code/virtualship`
* `repository_owner`: `Parcels-code`
* `repository_owner_id`: `14887518`
* `workflow_ref`: `Parcels-code/virtualship/.github/workflows/cd.yml@refs/tags/0.2.1`
* `job_workflow_ref`: `Parcels-code/virtualship/.github/workflows/cd.yml@refs/tags/0.2.1`
* `ref`: `refs/tags/0.2.1`
* `environment`: `pypi`
See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
Package Metadata
|
3.06 KB |
sha256:9e34826d81aa11ef510448bbf841e8341fec36a15c2b6e01f217c112fccf7ef2
|
|
|
Packages
|
5.88 MB |
sha256:fd736c47b163c4e9e77a7c52656c282ee04106c9e50fc772ee44ca6db0ef9038
|
|
|
PyPI README
|
1.92 KB |
sha256:40efb56e051146901251f140080454ce7054a814070b456e81672e32ed604def
|
|