fix: add ncurses lib target #107
jaromilmain.yml
on: push
Annotations
7 errors and 12 warnings
|
🐧 Build release (riscv64-linux-musl, riscv_64)
Process completed with exit code 2.
|
|
🐧 Build release (x86_64-linux-musl, x86_64)
The strategy configuration was canceled because "gcc-musl-build.riscv64-linux-musl_riscv_" failed
|
|
🐧 Build release (x86_64-linux-musl, x86_64)
The operation was canceled.
|
|
🐧 Build release (arm-linux-musleabihf, arm_hf)
The strategy configuration was canceled because "gcc-musl-build.riscv64-linux-musl_riscv_" failed
|
|
🐧 Build release (arm-linux-musleabihf, arm_hf)
The operation was canceled.
|
|
🐧 Build release (aarch64-linux-musl, arm_64)
The strategy configuration was canceled because "gcc-musl-build.riscv64-linux-musl_riscv_" failed
|
|
🐧 Build release (aarch64-linux-musl, arm_64)
The operation was canceled.
|
|
🐧 Build release (riscv64-linux-musl, riscv_64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hendrikmuhs/ccache-action@v1.2. 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 release (riscv64-linux-musl, riscv_64)
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
|
|
🐧 Build release (x86_64-linux-musl, x86_64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hendrikmuhs/ccache-action@v1.2. 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 release (x86_64-linux-musl, x86_64)
Failed to save: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 1
|
|
🐧 Build release (x86_64-linux-musl, x86_64)
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
|
|
🐧 Build release (arm-linux-musleabihf, arm_hf)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hendrikmuhs/ccache-action@v1.2. 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 release (arm-linux-musleabihf, arm_hf)
Failed to save: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 1
|
|
🐧 Build release (arm-linux-musleabihf, arm_hf)
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
|
|
🐧 Build release (aarch64-linux-musl, arm_64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hendrikmuhs/ccache-action@v1.2. 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 release (aarch64-linux-musl, arm_64)
Failed to save: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 1
|
|
🐧 Build release (aarch64-linux-musl, arm_64)
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
|
|
🧻 Remove tag on fail
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dev-drprasad/delete-tag-and-release@v1.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/
|