v0.11.0-rc2 #2
Triggered via release
April 7, 2026 02:36
GrandpaEJ
published
v0.11.0-rc2
Status
Success
Total duration
23s
Artifacts
–
Annotations
1 error and 4 warnings
|
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:RUSTxPY/BustAPI:environment:pypi`
* `repository`: `RUSTxPY/BustAPI`
* `repository_owner`: `RUSTxPY`
* `repository_owner_id`: `265328331`
* `workflow_ref`: `RUSTxPY/BustAPI/.github/workflows/manual-publish.yml@refs/tags/v0.11.0-rc2`
* `job_workflow_ref`: `RUSTxPY/BustAPI/.github/workflows/manual-publish.yml@refs/tags/v0.11.0-rc2`
* `ref`: `refs/tags/v0.11.0-rc2`
* `environment`: `pypi`
See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
|
|
Publish to PyPI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dawidd6/action-download-artifact@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Create a Trusted Publisher
A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):
|
|
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
|
|
attestations input ignored
The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.
|