0.2.1 Better AI API and special error handling, performance and other… #4
Deployment protection rules
Reviewers, timers, and other rules protecting deployments in this run
Event | Environments |
---|---|
Wait timer
completed
|
release |
Annotations
1 error and 1 warning
build-and-publish
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:matebenyovszky/healing-agent:environment:release`
* `repository`: `matebenyovszky/healing-agent`
* `repository_owner`: `matebenyovszky`
* `repository_owner_id`: `57362482`
* `job_workflow_ref`: `matebenyovszky/healing-agent/.github/workflows/python-publish.yml@refs/tags/v0.2.2`
* `ref`: `refs/tags/v0.2.2`
See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
|
build-and-publish
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|