Skip to content

Release / Publish Pipeline #8

Release / Publish Pipeline

Release / Publish Pipeline #8

Triggered via release April 5, 2026 08:04
@ThreeFish-AIThreeFish-AI
published f784a37
Status Failure
Total duration 19s
Artifacts 1

release.yml

on: release
Matrix: Build distributions
Publish to PyPI
0s
Publish to PyPI
Publish to TestPyPI
0s
Publish to TestPyPI
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 7 warnings
Build distributions (3.13)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
Build distributions (3.12)
The strategy configuration was canceled because "build._3_13" failed
Build distributions (3.14)
The strategy configuration was canceled because "build._3_13" failed
Build distributions (3.14)
The operation was canceled.
Build distributions (3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4, astral-sh/setup-uv@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build distributions (3.13)
Failed to restore: Cache service responded with 400
Build distributions (3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4, astral-sh/setup-uv@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build distributions (3.12)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0hhfSaQAAAACI0L9A0KJcRbBT4ImBumObQ0hHRURHRTE4MTgARWRnZQ==
Build distributions (3.12)
Failed to restore: Cache service responded with 400
Build distributions (3.14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4, astral-sh/setup-uv@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build distributions (3.14)
Failed to restore: Cache service responded with 400

Artifacts

Produced during runtime
Name Size Digest
dist Expired
409 KB
sha256:4e7009b64dd1bb13dd274a789d32ca2622931a86fbcf4403f8cbe56f5c4e9abd