Skip to content

bump version

bump version #18

Triggered via push May 8, 2026 09:15
Status Failure
Total duration 1m 56s
Artifacts

release.yml

on: push
Matrix: Build for multiple targets
Create GitHub Release
Create GitHub Release
Fit to window
Zoom out
Zoom in

Annotations

13 errors and 7 warnings
Build for multiple targets (x86_64-unknown-linux-gnu)
Process completed with exit code 101.
Build for multiple targets (x86_64-unknown-freebsd)
The strategy configuration was canceled because "build.x86_64-unknown-linux-gnu" failed
Build for multiple targets (x86_64-unknown-freebsd)
The operation was canceled.
Build for multiple targets (armv7-unknown-linux-musleabi)
The strategy configuration was canceled because "build.x86_64-unknown-linux-gnu" failed
Build for multiple targets (armv7-unknown-linux-musleabi)
The operation was canceled.
Build for multiple targets (aarch64-unknown-linux-musl)
The strategy configuration was canceled because "build.x86_64-unknown-linux-gnu" failed
Build for multiple targets (aarch64-unknown-linux-musl)
The operation was canceled.
Build for multiple targets (armv7-unknown-linux-gnueabi)
The strategy configuration was canceled because "build.x86_64-unknown-linux-gnu" failed
Build for multiple targets (armv7-unknown-linux-gnueabi)
The operation was canceled.
Build for multiple targets (aarch64-unknown-linux-gnu)
The strategy configuration was canceled because "build.x86_64-unknown-linux-gnu" failed
Build for multiple targets (aarch64-unknown-linux-gnu)
The operation was canceled.
Build for multiple targets (x86_64-unknown-linux-musl)
The strategy configuration was canceled because "build.x86_64-unknown-linux-gnu" failed
Build for multiple targets (x86_64-unknown-linux-musl)
The operation was canceled.
Build for multiple targets (x86_64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, mathiasvr/command-output@v2.0.0. 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 for multiple targets (x86_64-unknown-freebsd)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, mathiasvr/command-output@v2.0.0. 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 for multiple targets (armv7-unknown-linux-musleabi)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, mathiasvr/command-output@v2.0.0. 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 for multiple targets (aarch64-unknown-linux-musl)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, mathiasvr/command-output@v2.0.0. 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 for multiple targets (armv7-unknown-linux-gnueabi)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, mathiasvr/command-output@v2.0.0. 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 for multiple targets (aarch64-unknown-linux-gnu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, mathiasvr/command-output@v2.0.0. 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 for multiple targets (x86_64-unknown-linux-musl)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, mathiasvr/command-output@v2.0.0. 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/