Build and/or Publish #1
Triggered via release
February 17, 2024 02:04
aaronsteers
published
7534fb2
Status
Failure
Total duration
51s
Artifacts
–
Annotations
1 error, 1 warning, and 1 notice
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 (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:airbytehq/PyAirbyte:environment:PyPi`
* `repository`: `airbytehq/PyAirbyte`
* `repository_owner`: `airbytehq`
* `repository_owner_id`: `59758427`
* `job_workflow_ref`: `airbytehq/PyAirbyte/.github/workflows/pypi_publish.yml@refs/tags/v0.0.1.dev0`
* `ref`: `refs/tags/v0.0.1.dev0`
|
publish-to-pypi
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: Gr1N/setup-poetry@v8. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
publish-to-pypi
Attempting to perform trusted publishing exchange to retrieve a temporary short-lived API token for authentication against https://upload.pypi.org/legacy/ due to __token__ username with no supplied password field
|