Skip to content

Add hatch auth&user env to publish workflow #3

Add hatch auth&user env to publish workflow

Add hatch auth&user env to publish workflow #3

Triggered via push June 16, 2024 21:53
Status Failure
Total duration 55s
Artifacts

publish.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
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:ayalash/reference_counter:environment:release` * `repository`: `ayalash/reference_counter` * `repository_owner`: `ayalash` * `repository_owner_id`: `1003519` * `job_workflow_ref`: `ayalash/reference_counter/.github/workflows/publish.yml@refs/tags/1.0.2` * `ref`: `refs/tags/1.0.2` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
deploy
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-python@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.