Skip to content

fix(ci): correct homebrew releaser inputs #11

fix(ci): correct homebrew releaser inputs

fix(ci): correct homebrew releaser inputs #11

Triggered via push March 17, 2026 23:51
Status Cancelled
Total duration 3m 2s
Artifacts

ci.yml

on: push
Verify CLI
51s
Verify CLI
Release CLI
34s
Release CLI
Matrix: build-unix-binaries
Build windows-latest release assets
1m 27s
Build windows-latest release assets
Update Homebrew tap
32s
Update Homebrew tap
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 5 warnings
Build windows-latest release assets
Canceling since a higher priority waiting request for ci-CI-refs/heads/main exists
Build windows-latest release assets
The operation was canceled.
CI
Canceling since a higher priority waiting request for ci-CI-refs/heads/main exists
Verify CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: voidzero-dev/setup-vp@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Release CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: cycjimmy/semantic-release-action@v4, voidzero-dev/setup-vp@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 ubuntu-latest release assets
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: softprops/action-gh-release@v2, voidzero-dev/setup-vp@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 macos-latest release assets
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: softprops/action-gh-release@v2, voidzero-dev/setup-vp@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 windows-latest release assets
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: voidzero-dev/setup-vp@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/