Skip to content

chore: release v0.6.1 - security hardening patch #9

chore: release v0.6.1 - security hardening patch

chore: release v0.6.1 - security hardening patch #9

Triggered via push March 15, 2026 06:56
Status Failure
Total duration 1m 11s
Artifacts

release.yml

on: push
Matrix: Build Release Binaries
Create GitHub Release
0s
Create GitHub Release
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 4 warnings
Build Release Binaries (x86_64-unknown-linux-gnu, ubuntu-latest, naru-linux-x64)
Process completed with exit code 1.
Build Release Binaries (x86_64-pc-windows-msvc, windows-latest, naru-windows-x64.exe)
The strategy configuration was canceled because "build.x86_64-unknown-linux-gnu_" failed
Build Release Binaries (x86_64-apple-darwin, macos-latest, naru-macos-x64)
The strategy configuration was canceled because "build.x86_64-unknown-linux-gnu_" failed
Build Release Binaries (aarch64-apple-darwin, macos-latest, naru-macos-arm64)
The strategy configuration was canceled because "build.x86_64-unknown-linux-gnu_" failed
Build Release Binaries (x86_64-unknown-linux-gnu, ubuntu-latest, naru-linux-x64)
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 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 Release Binaries (x86_64-pc-windows-msvc, windows-latest, naru-windows-x64.exe)
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 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 Release Binaries (x86_64-apple-darwin, macos-latest, naru-macos-x64)
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 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 Release Binaries (aarch64-apple-darwin, macos-latest, naru-macos-arm64)
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 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/