This repository was archived by the owner on Apr 29, 2026. It is now read-only.
Nightly build #704
Joshua-RiekAnnotations
201 errors and 47 warnings
|
Build image (nanopc-t6, oracular, server)
Process completed with exit code 32.
|
|
Build image (armsom-aim7, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (armsom-w3, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (armsom-sige5, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (armsom-sige7, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (lubancat-4, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (armsom-sige7, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (mixtile-blade3, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (lubancat-4, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (lubancat-4, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (mixtile-core3588e, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (nanopi-r6c, plucky, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (nanopi-r6c, oracular, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (mixtile-core3588e, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (mixtile-core3588e, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (nanopc-t6, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (nanopi-r6c, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (nanopi-r6s, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (nanopi-r6s, plucky, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (nanopi-r6c, oracular, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-5-max, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (nanopi-r6s, oracular, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-3b, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (nanopi-r6s, oracular, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-3b, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-5-plus, oracular, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (nanopi-r6s, plucky, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-5-max, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-3b, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-5-plus, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (armsom-aim7, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (armsom-aim7, noble, desktop)
The operation was canceled.
|
|
Build image (armsom-w3, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" 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.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-3b, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-5-plus, oracular, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-5-max, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-5-plus, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-5-pro, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-5, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-5-pro, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (armsom-sige7, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-5, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (armsom-sige7, noble, desktop)
The operation was canceled.
|
|
Build image (orangepi-5, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (lubancat-4, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (indiedroid-nova, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (lubancat-4, jammy, desktop)
The operation was canceled.
|
|
Build image (indiedroid-nova, noble, desktop)
The operation was canceled.
|
|
Build image (orangepi-5, oracular, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-5, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-5-plus, plucky, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-5-pro, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-5b, oracular, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-5, oracular, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-5b, oracular, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-5b, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-cm5, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-5b, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-5, plucky, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-5b, plucky, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-5b, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (radxa-cm5-io, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-5b, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (armsom-sige7, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (armsom-sige7, jammy, server)
The operation was canceled.
|
|
Build image (orangepi-cm5, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (radxa-cm5-io, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-cm5, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (armsom-sige5, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-5, plucky, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (armsom-sige5, noble, server)
The operation was canceled.
|
|
Build image (orangepi-5b, plucky, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (radxa-cm5-io, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-cm5, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (radxa-cm5-rpi-cm4-io, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (radxa-cm5-io, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (radxa-cm5-rpi-cm4-io, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (radxa-zero3, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (radxa-nx5-io, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (radxa-zero3, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (radxa-nx5-io, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (radxa-nx5-io, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (radxa-cm5-rpi-cm4-io, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (radxa-cm5-rpi-cm4-io, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (radxa-zero3, plucky, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (radxa-zero3, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (nanopi-r6s, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (nanopi-r6s, jammy, desktop)
The operation was canceled.
|
|
Build image (roc-rk3588s-pc, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (radxa-nx5-io, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5-itx, plucky, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (roc-rk3588s-pc, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (radxa-zero3, plucky, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5-itx, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (roc-rk3588s-pc, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (nanopi-r6s, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (roc-rk3588s-pc, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (nanopi-r6s, noble, server)
The operation was canceled.
|
|
Build image (rock-5-itx, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5-itx, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5-itx, plucky, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (radxa-zero3, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5a, oracular, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5a, oracular, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5b-plus, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5a, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5a, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (mixtile-blade3, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (mixtile-blade3, jammy, server)
The operation was canceled.
|
|
Build image (rock-5a, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5-itx, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5b-plus, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5a, plucky, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5a, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5b-plus, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5a, plucky, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (armsom-w3, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (armsom-w3, jammy, desktop)
The operation was canceled.
|
|
Build image (rock-5b, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5b, oracular, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5b, plucky, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5b-plus, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5b, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5c, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5b, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5c, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5b, plucky, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5b, oracular, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5b, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-5-plus, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5d, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-5-plus, noble, desktop)
The operation was canceled.
|
|
Build image (rock-5d, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5c, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (turing-rk1, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (turing-rk1, plucky, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5d, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5c, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (turing-rk1, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (turing-rk1, plucky, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (turing-rk1, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (turing-rk1, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (turing-rk1, oracular, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (rock-5d, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (turing-rk1, oracular, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (nanopc-t6, oracular, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (nanopc-t6, oracular, desktop)
The operation was canceled.
|
|
Build image (aio-3588l, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (aio-3588l, jammy, server)
The operation was canceled.
|
|
Build image (mixtile-blade3, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (mixtile-blade3, noble, server)
The operation was canceled.
|
|
Build image (nanopi-r6c, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (nanopi-r6c, jammy, desktop)
The operation was canceled.
|
|
Build image (indiedroid-nova, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (indiedroid-nova, jammy, desktop)
The operation was canceled.
|
|
Build image (armsom-aim7, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (armsom-aim7, jammy, server)
The operation was canceled.
|
|
Build image (aio-3588l, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (aio-3588l, noble, desktop)
The operation was canceled.
|
|
Build image (aio-3588l, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (aio-3588l, noble, server)
The operation was canceled.
|
|
Build image (nanopc-t6, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (nanopc-t6, jammy, server)
The operation was canceled.
|
|
Build image (armsom-aim7, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (armsom-aim7, noble, server)
The operation was canceled.
|
|
Build image (armsom-w3, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (armsom-w3, noble, server)
The operation was canceled.
|
|
Build image (nanopi-r6c, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (aio-3588l, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (nanopi-r6c, jammy, server)
The operation was canceled.
|
|
Build image (aio-3588l, jammy, desktop)
The operation was canceled.
|
|
Build image (mixtile-blade3, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (mixtile-blade3, noble, desktop)
The operation was canceled.
|
|
Build image (orangepi-5-pro, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-5-pro, noble, server)
The operation was canceled.
|
|
Build image (mixtile-core3588e, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (mixtile-core3588e, noble, desktop)
The operation was canceled.
|
|
Build image (nanopc-t6, plucky, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (nanopc-t6, plucky, server)
The operation was canceled.
|
|
Build image (nanopi-r6c, plucky, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (nanopi-r6c, plucky, server)
The operation was canceled.
|
|
Build image (indiedroid-nova, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (indiedroid-nova, noble, server)
The operation was canceled.
|
|
Build image (indiedroid-nova, jammy, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (indiedroid-nova, jammy, server)
The operation was canceled.
|
|
Build image (nanopc-t6, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (nanopc-t6, noble, server)
The operation was canceled.
|
|
Build image (nanopc-t6, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (nanopc-t6, jammy, desktop)
The operation was canceled.
|
|
Build image (nanopi-r6s, noble, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (nanopi-r6s, noble, desktop)
The operation was canceled.
|
|
Build image (nanopc-t6, plucky, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (nanopc-t6, plucky, desktop)
The operation was canceled.
|
|
Build image (orangepi-5-plus, jammy, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-5-plus, jammy, desktop)
The operation was canceled.
|
|
Build image (nanopi-r6c, noble, server)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (orangepi-5-plus, plucky, desktop)
The strategy configuration was canceled because "build.nanopc-t6_oracular_server" failed
|
|
Build image (nanopi-r6c, noble, server)
The operation was canceled.
|
|
Build image (orangepi-5-plus, plucky, desktop)
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 (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, 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, 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, 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 (lubancat-4, 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 (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-sige5, 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, 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, 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, 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 (orangepi-5-plus, 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, 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 (aio-3588l, 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 (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 (nanopi-r6c, 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, 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 (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 (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 (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 (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 (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 (nanopi-r6c, 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 (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 (mixtile-blade3, 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-pro, 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, 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, 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/
|
|
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 (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, 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 (nanopc-t6, 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, 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 (orangepi-5-plus, 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-r6c, 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-5-plus, 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
ubuntu-22.04-preinstalled-desktop-arm64-rootfs
|
1.66 GB |
sha256:94fa8a5de376fcf4473d9a8972e78ab85545b57bb2ad3a13c56abc21d9493cd9
|
|
|
ubuntu-22.04-preinstalled-server-arm64-rootfs
|
865 MB |
sha256:3e82ffb5bde43ccc0ea73372b64bdd9745fdca057a42d3d6c729a04071d809f6
|
|
|
ubuntu-24.04-preinstalled-desktop-arm64-rootfs
|
1.99 GB |
sha256:5285b132e60c73c59f282aefc3338b948f291595a7e352a9d333e0334e013d3f
|
|
|
ubuntu-24.04-preinstalled-server-arm64-rootfs
|
994 MB |
sha256:77538749edd162cf15311200e20adbde5d803bc112eac23a9b796f3de5320030
|
|
|
ubuntu-24.10-preinstalled-desktop-arm64-rootfs
|
252 Bytes |
sha256:6d002b17fffd098d1e2e0a13298081ad8780e00213b7f3a2a66c891e017ddd15
|
|
|
ubuntu-24.10-preinstalled-server-arm64-rootfs
|
250 Bytes |
sha256:821976cc2e8934b33ee50692376293c3c63e072dc0b2f69ed70a4f4eb207624c
|
|
|
ubuntu-25.04-preinstalled-desktop-arm64-rootfs
|
1.98 GB |
sha256:ff732fdaace7fd900c2ba0c3e92f15294f8598b30c0228dd17da201e0d9ae80a
|
|
|
ubuntu-25.04-preinstalled-server-arm64-rootfs
|
969 MB |
sha256:7999df8dd46d3deeaaf413af6dbf62ab9e2fd1e9ff02fd5003c512cbdd5cf5d9
|
|