3.6.0-rc1.post1 #24
Triggered via release
March 25, 2025 17:21
AndyEveritt
published
3.6.0-rc1.post1
Status
Failure
Total duration
36s
Artifacts
1
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
publish-to-pypi.yml
on: release
Build distribution π¦
11s
Build Debian package π¦
26s
Publish Python π distribution π¦ to PyPI
14s
Annotations
2 errors
|
Build Debian package π¦
Process completed with exit code 1.
|
|
Publish Python π distribution π¦ 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 (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:Duet3D/dsf-python:ref:refs/tags/3.6.0-rc1.post1`
* `repository`: `Duet3D/dsf-python`
* `repository_owner`: `Duet3D`
* `repository_owner_id`: `59487011`
* `workflow_ref`: `Duet3D/dsf-python/.github/workflows/publish-to-pypi.yml@refs/tags/3.6.0-rc1.post1`
* `job_workflow_ref`: `Duet3D/dsf-python/.github/workflows/publish-to-pypi.yml@refs/tags/3.6.0-rc1.post1`
* `ref`: `refs/tags/3.6.0-rc1.post1`
See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
python-package-distributions
Expired
|
212 KB |
sha256:e3c397dbcb4c8ecae479e4774117456467e8ae8ce96c23449603e32760731660
|
|