Process completed with exit code 1.

Process completed with exit code 1.

Version verification failed! Update workspace.package.version in Cargo.toml to match the release tag.

Version mismatch for terraphim_grep: expected 1.20.4, got 1.20.3

Version mismatch for terraphim-cli: expected 1.20.4, got 1.20.3

Version mismatch for terraphim_agent: expected 1.20.4, got 1.20.3

Version mismatch for terraphim_server: expected 1.20.4, got 1.20.3

The ref 'refs/tags/v1.20.4' does not point to the expected commit '018d186062255221e396e10c5bf1cad7115148ff'. The ref may have been updated after the workflow was triggered.

The ref 'refs/tags/v1.20.4' does not point to the expected commit '018d186062255221e396e10c5bf1cad7115148ff'. The ref may have been updated after the workflow was triggered.

The ref 'refs/tags/v1.20.4' does not point to the expected commit '018d186062255221e396e10c5bf1cad7115148ff'. The ref may have been updated after the workflow was triggered.

The ref 'refs/tags/v1.20.4' does not point to the expected commit '018d186062255221e396e10c5bf1cad7115148ff'. The ref may have been updated after the workflow was triggered.

The ref 'refs/tags/v1.20.4' does not point to the expected commit '018d186062255221e396e10c5bf1cad7115148ff'. The ref may have been updated after the workflow was triggered.

/Users/alex/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/rustc: /Users/alex/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/rustc: cannot execute binary file

Command failed: rustup run stable-x86_64-unknown-linux-gnu rustc -vV

The ref 'refs/tags/v1.20.4' does not point to the expected commit '018d186062255221e396e10c5bf1cad7115148ff'. The ref may have been updated after the workflow was triggered.

Process completed with exit code 1.

Unable to download artifact(s): Artifact not found for name: binaries-aarch64-apple-darwin Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact. For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 1password/install-cli-action@v2. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/