Publish to PyPI #9
Deployment protection rules
Reviewers, timers, and other rules protecting deployments in this run
Event | Environments |
---|---|
wesselb
approved
|
publish-to-pypi |
Annotations
1 error and 2 warnings
deploy
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:microsoft/Aurora:environment:publish-to-pypi`
* `repository`: `microsoft/Aurora`
* `repository_owner`: `microsoft`
* `repository_owner_id`: `6154722`
* `job_workflow_ref`: `microsoft/Aurora/.github/workflows/publish.yaml@refs/tags/v0.0.0`
* `ref`: `refs/tags/v0.0.0`
See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
|
deploy
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
deploy
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|