build: handle PyPi versioning scheme for library versioning #49
libnvme-release-python.yml
on: push
Build source distribution
31s
Build test source distribution
38s
upload_pypi
0s
upload_test_pypi
14s
Annotations
1 error
|
upload_test_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:linux-nvme/nvme-cli:environment:pypi`
* `repository`: `linux-nvme/nvme-cli`
* `repository_owner`: `linux-nvme`
* `repository_owner_id`: `10873541`
* `workflow_ref`: `linux-nvme/nvme-cli/.github/workflows/libnvme-release-python.yml@refs/heads/master`
* `job_workflow_ref`: `linux-nvme/nvme-cli/.github/workflows/libnvme-release-python.yml@refs/heads/master`
* `ref`: `refs/heads/master`
* `environment`: `pypi`
See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
artifact
Expired
|
2.07 MB |
sha256:1e13562be5a0983e1f354891c0149f572095e4909782361cb5624573308718e4
|
|
|
test_pypi
Expired
|
2.07 MB |
sha256:398e4a7c63b89d034e7c05e99933c16f08abb4ba4dd8dbca8ee02477af930d3e
|
|