Skip to content

update release date for 0.34.6 #11

update release date for 0.34.6

update release date for 0.34.6 #11

Triggered via push August 1, 2024 14:55
Status Failure
Total duration 51s
Artifacts 1

release.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
Publish distribution packages ? 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:larray-project/larray:environment:pypi` * `repository`: `larray-project/larray` * `repository_owner`: `larray-project` * `repository_owner_id`: `26460981` * `job_workflow_ref`: `larray-project/larray/.github/workflows/release.yml@refs/tags/0.34.6` * `ref`: `refs/tags/0.34.6` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
Publish distribution packages ? to TestPyPI
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:larray-project/larray:environment:testpypi` * `repository`: `larray-project/larray` * `repository_owner`: `larray-project` * `repository_owner_id`: `26460981` * `job_workflow_ref`: `larray-project/larray/.github/workflows/release.yml@refs/tags/0.34.6` * `ref`: `refs/tags/0.34.6` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
Build distribution packages ?
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Publish distribution packages ? to PyPI
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/download-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "python-distribution-packages". 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/
Publish distribution packages ? to TestPyPI
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/download-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
python-distribution-packages Expired
4.9 MB