MAINT automate the pypi release process with CI and trusted publishin… #1
publish_to_pypi.yml
on: push
Build distribution 📦
10s
Publish Python 🐍 distribution 📦 to TestPyPI
9s
Sign the Python 🐍 distribution 📦 with Sigstore and upload them to GitHub Release
0s
Annotations
1 error and 1 warning
Publish Python 🐍 distribution 📦 to TestPyPI
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:cloudpipe/cloudpickle:environment:testpypi`
* `repository`: `cloudpipe/cloudpickle`
* `repository_owner`: `cloudpipe`
* `repository_owner_id`: `10352495`
* `workflow_ref`: `cloudpipe/cloudpickle/.github/workflows/publish_to_pypi.yml@refs/heads/master`
* `job_workflow_ref`: `cloudpipe/cloudpickle/.github/workflows/publish_to_pypi.yml@refs/heads/master`
* `ref`: `refs/heads/master`
See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
|
Build distribution 📦
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
python-package-distributions
|
41.9 KB |
|