Skip to content
This repository was archived by the owner on Apr 29, 2026. It is now read-only.

Nightly build

Nightly build #686

Triggered via schedule April 8, 2026 00:10
Status Failure
Total duration 3h 13m 24s
Artifacts 8

nightly.yml

on: schedule
Create martrix
6s
Create martrix
Matrix: Build rootfs
Matrix: Build image
Fit to window
Zoom out
Zoom in

Annotations

201 errors and 48 warnings
Build image (orangepi-5-plus, oracular, server)
Process completed with exit code 32.
Build image (armsom-sige5, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (armsom-w3, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (mixtile-blade3, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (mixtile-blade3, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (lubancat-4, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (nanopi-r6c, oracular, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (nanopc-t6, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (indiedroid-nova, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (lubancat-4, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (nanopc-t6, plucky, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (nanopi-r6c, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (nanopi-r6c, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-3b, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (nanopi-r6c, oracular, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (nanopc-t6, oracular, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (nanopi-r6c, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-3b, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5-plus, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (nanopi-r6s, plucky, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (nanopi-r6s, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (nanopi-r6c, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (mixtile-core3588e, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (nanopi-r6s, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5-max, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5-max, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5-max, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5-pro, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-3b, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5-plus, oracular, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5-plus, plucky, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (aio-3588l, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (nanopi-r6s, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (aio-3588l, noble, desktop)
The operation was canceled.
Build image (nanopi-r6s, plucky, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5-pro, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5-plus, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5-plus, plucky, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5-plus, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-3b, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5, plucky, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5, oracular, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5b, oracular, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5b, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5-plus, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (radxa-cm5-io, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5-pro, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5b, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-cm5, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-cm5, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (radxa-cm5-rpi-cm4-io, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5b, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5b, oracular, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5, oracular, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5, plucky, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (radxa-cm5-io, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (radxa-cm5-rpi-cm4-io, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5b, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-cm5, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5b, plucky, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (radxa-cm5-io, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-cm5, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (radxa-cm5-io, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (radxa-zero3, plucky, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (roc-rk3588s-pc, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (radxa-nx5-io, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (radxa-zero3, plucky, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (radxa-cm5-rpi-cm4-io, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (radxa-nx5-io, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (radxa-cm5-rpi-cm4-io, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (radxa-nx5-io, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (mixtile-blade3, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (radxa-zero3, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (mixtile-blade3, jammy, desktop)
The operation was canceled.
Build image (radxa-nx5-io, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (mixtile-core3588e, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (mixtile-core3588e, jammy, desktop)
The operation was canceled.
Build image (roc-rk3588s-pc, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5a, plucky, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5-itx, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (roc-rk3588s-pc, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (radxa-zero3, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (radxa-zero3, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5a, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5-itx, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (indiedroid-nova, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (indiedroid-nova, noble, desktop)
The operation was canceled.
Build image (roc-rk3588s-pc, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (nanopc-t6, plucky, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (nanopc-t6, plucky, desktop)
The operation was canceled.
Build image (rock-5b-plus, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5-itx, plucky, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5-itx, plucky, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5a, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5b, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5b, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (radxa-zero3, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5b, oracular, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5b-plus, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5b, plucky, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5a, oracular, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5-itx, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5a, plucky, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5b, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5a, oracular, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5a, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5-itx, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5b-plus, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5b-plus, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (armsom-sige7, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5b, plucky, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5d, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (armsom-sige7, noble, desktop)
The operation was canceled.
Build image (rock-5a, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5d, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5c, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5c, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5b, oracular, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5c, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5b, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (turing-rk1, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (turing-rk1, oracular, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5d, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (turing-rk1, plucky, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (turing-rk1, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (nanopi-r6c, plucky, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (nanopi-r6c, plucky, desktop)
The operation was canceled.
Build image (turing-rk1, oracular, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5d, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (rock-5c, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (armsom-sige5, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (turing-rk1, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (armsom-sige5, noble, desktop)
The operation was canceled.
Build image (turing-rk1, plucky, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (turing-rk1, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (indiedroid-nova, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (indiedroid-nova, noble, server)
The operation was canceled.
Build image (mixtile-blade3, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (mixtile-blade3, noble, server)
The operation was canceled.
Build image (orangepi-5b, plucky, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5b, plucky, desktop)
The operation was canceled.
Build image (armsom-aim7, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (armsom-aim7, jammy, desktop)
The operation was canceled.
Build image (aio-3588l, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (aio-3588l, jammy, desktop)
The operation was canceled.
Build image (nanopc-t6, oracular, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (nanopc-t6, oracular, server)
The operation was canceled.
Build image (armsom-aim7, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (armsom-aim7, noble, server)
The operation was canceled.
Build image (lubancat-4, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (lubancat-4, jammy, server)
The operation was canceled.
Build image (armsom-sige7, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (armsom-sige7, jammy, desktop)
The operation was canceled.
Build image (aio-3588l, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (aio-3588l, noble, server)
The operation was canceled.
Build image (armsom-aim7, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (armsom-aim7, jammy, server)
The operation was canceled.
Build image (armsom-aim7, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (armsom-aim7, noble, desktop)
The operation was canceled.
Build image (armsom-w3, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (armsom-w3, jammy, server)
The operation was canceled.
Build image (armsom-sige7, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (armsom-sige7, jammy, server)
The operation was canceled.
Build image (armsom-w3, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (armsom-w3, noble, server)
The operation was canceled.
Build image (lubancat-4, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (lubancat-4, noble, desktop)
The operation was canceled.
Build image (nanopc-t6, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (armsom-sige7, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (nanopc-t6, noble, desktop)
The operation was canceled.
Build image (armsom-sige7, noble, server)
The operation was canceled.
Build image (mixtile-core3588e, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (mixtile-core3588e, jammy, server)
The operation was canceled.
Build image (armsom-w3, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (armsom-w3, noble, desktop)
The operation was canceled.
Build image (orangepi-5-max, noble, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5-max, noble, desktop)
The operation was canceled.
Build image (nanopi-r6s, oracular, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (nanopi-r6s, oracular, desktop)
The operation was canceled.
Build image (mixtile-core3588e, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (mixtile-core3588e, noble, server)
The operation was canceled.
Build image (nanopi-r6s, jammy, desktop)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (aio-3588l, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (aio-3588l, jammy, server)
The operation was canceled.
Build image (nanopi-r6s, jammy, desktop)
The operation was canceled.
Build image (nanopi-r6s, oracular, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (nanopi-r6s, oracular, server)
The operation was canceled.
Build image (nanopc-t6, noble, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (nanopc-t6, noble, server)
The operation was canceled.
Build image (indiedroid-nova, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (indiedroid-nova, jammy, server)
The operation was canceled.
Build image (nanopc-t6, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (nanopc-t6, jammy, server)
The operation was canceled.
Build image (orangepi-5-pro, jammy, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (orangepi-5-pro, jammy, server)
The operation was canceled.
Build image (nanopi-r6c, plucky, server)
The strategy configuration was canceled because "build.orangepi-5-plus_oracular_" failed
Build image (nanopi-r6c, plucky, server)
The operation was canceled.
Create martrix
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. 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 rootfs (oracular, server)
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/upload-artifact@v4.3.3. 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 rootfs (oracular, desktop)
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/upload-artifact@v4.3.3. 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 rootfs (jammy, server)
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/upload-artifact@v4.3.3. 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 rootfs (jammy, desktop)
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/upload-artifact@v4.3.3. 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 rootfs (plucky, server)
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/upload-artifact@v4.3.3. 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 rootfs (noble, server)
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/upload-artifact@v4.3.3. 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 rootfs (plucky, desktop)
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/upload-artifact@v4.3.3. 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 rootfs (noble, desktop)
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/upload-artifact@v4.3.3. 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 image (orangepi-5-plus, oracular, server)
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/download-artifact@v4.1.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 image (aio-3588l, noble, desktop)
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/download-artifact@v4.1.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 image (mixtile-blade3, jammy, desktop)
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/download-artifact@v4.1.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 image (mixtile-core3588e, jammy, desktop)
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/download-artifact@v4.1.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 image (indiedroid-nova, noble, desktop)
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/download-artifact@v4.1.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 image (nanopc-t6, plucky, desktop)
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/download-artifact@v4.1.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 image (armsom-sige7, noble, desktop)
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/download-artifact@v4.1.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 image (nanopi-r6c, plucky, desktop)
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/download-artifact@v4.1.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 image (armsom-sige5, noble, desktop)
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/download-artifact@v4.1.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 image (indiedroid-nova, noble, server)
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/download-artifact@v4.1.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 image (mixtile-blade3, noble, server)
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/download-artifact@v4.1.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 image (orangepi-5b, plucky, desktop)
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/download-artifact@v4.1.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 image (armsom-aim7, jammy, desktop)
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/download-artifact@v4.1.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 image (aio-3588l, jammy, desktop)
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/download-artifact@v4.1.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 image (nanopc-t6, oracular, server)
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/download-artifact@v4.1.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 image (armsom-aim7, noble, server)
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/download-artifact@v4.1.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 image (lubancat-4, jammy, server)
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/download-artifact@v4.1.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 image (armsom-sige7, jammy, desktop)
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/download-artifact@v4.1.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 image (aio-3588l, noble, server)
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/download-artifact@v4.1.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 image (armsom-aim7, jammy, server)
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/download-artifact@v4.1.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 image (armsom-aim7, noble, desktop)
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/download-artifact@v4.1.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 image (armsom-w3, jammy, server)
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/download-artifact@v4.1.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 image (armsom-sige7, jammy, server)
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/download-artifact@v4.1.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 image (armsom-w3, noble, server)
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/download-artifact@v4.1.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 image (lubancat-4, noble, desktop)
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/download-artifact@v4.1.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 image (nanopc-t6, noble, desktop)
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/download-artifact@v4.1.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 image (armsom-sige7, noble, server)
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/download-artifact@v4.1.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 image (mixtile-core3588e, jammy, server)
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/download-artifact@v4.1.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 image (armsom-w3, noble, desktop)
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/download-artifact@v4.1.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 image (orangepi-5-max, noble, desktop)
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/download-artifact@v4.1.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 image (nanopi-r6s, oracular, desktop)
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/download-artifact@v4.1.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 image (mixtile-core3588e, noble, server)
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/download-artifact@v4.1.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 image (nanopi-r6s, jammy, desktop)
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/download-artifact@v4.1.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 image (nanopi-r6s, oracular, server)
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/download-artifact@v4.1.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 image (nanopc-t6, noble, server)
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/download-artifact@v4.1.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 image (indiedroid-nova, jammy, server)
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/download-artifact@v4.1.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 image (nanopc-t6, jammy, server)
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/download-artifact@v4.1.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 image (orangepi-5-pro, jammy, server)
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/download-artifact@v4.1.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 image (nanopi-r6c, plucky, server)
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/download-artifact@v4.1.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/

Artifacts

Produced during runtime
Name Size Digest
ubuntu-22.04-preinstalled-desktop-arm64-rootfs
1.65 GB
sha256:87020b3775f6d46376cf5ba78fe6d7deb8b9a725e0578ffd443f49e4ab2a78b4
ubuntu-22.04-preinstalled-server-arm64-rootfs
865 MB
sha256:d38792d575c6365bdcea4ab803dc48c30fd634d511b6d5b34f3e68d40b8d713b
ubuntu-24.04-preinstalled-desktop-arm64-rootfs
1.92 GB
sha256:79bffa82bee45d1f4d1cb55fecf31908080a3f37e62d6b0d8dedcd453b00e750
ubuntu-24.04-preinstalled-server-arm64-rootfs
925 MB
sha256:ceb1e92ed20b8d10e7d2c94f4ae1f36e28a00c9c0a955047a229899723b601ce
ubuntu-24.10-preinstalled-desktop-arm64-rootfs
252 Bytes
sha256:64bd0bec540b9b08aadbbecfca3a226e3d1c7e6fb6c9b70142cd3f67cb8bf6ac
ubuntu-24.10-preinstalled-server-arm64-rootfs
250 Bytes
sha256:26e5fffb73d8ac50a2209b598945d31a38aa278b3b158c60726a44bc23243ce9
ubuntu-25.04-preinstalled-desktop-arm64-rootfs
1.98 GB
sha256:52cd8d2110b071ab98053e1f24f019a6def1c8837a28d606639be377a93ab81a
ubuntu-25.04-preinstalled-server-arm64-rootfs
969 MB
sha256:dbb86792d2bca7eba662a8a2634d7392834082c91599e32bbb1cde5ddb77683a