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:mmzdouc/fermo_core:environment:pypi` * `repository`: `mmzdouc/fermo_core` * `repository_owner`: `mmzdouc` * `repository_owner_id`: `95709447` * `job_workflow_ref`: `mmzdouc/fermo_core/.github/workflows/publish_pypi.yml@refs/tags/0.1.0` * `ref`: `refs/tags/0.1.0` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "python-package-distributions". Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/