Skip to content

Update angular monorepo to v21.2.22 #427

Update angular monorepo to v21.2.22

Update angular monorepo to v21.2.22 #427

Triggered via pull request June 3, 2026 14:15
Status Failure
Total duration 6m 52s
Artifacts 5

build.yml

on: pull_request
Matrix: build-client / build
Matrix: build-server / build
build-client  /  merge
build-client / merge
build-server  /  merge
36s
build-server / merge
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 5 warnings
build-client / Build linux/amd64 Docker Image for ghcr.io/ls1intum/module-management/client
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c npm install" did not complete successfully: exit code: 1
build-client / Build linux/arm64 Docker Image for ghcr.io/ls1intum/module-management/client
The strategy configuration was canceled because "build-client.build.linux_amd64_ubuntu-24_04" failed
build-client / Build linux/amd64 Docker Image for ghcr.io/ls1intum/module-management/client
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-client / Build linux/arm64 Docker Image for ghcr.io/ls1intum/module-management/client
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-server / Build linux/amd64 Docker Image for ghcr.io/ls1intum/module-management/server
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-server / Build linux/arm64 Docker Image for ghcr.io/ls1intum/module-management/server
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-server / merge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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
digests-26890695543-ghcr.io-ls1intum-module-management-server-linux-amd64 Expired
244 Bytes
sha256:7e118252694a1b6a15ce44ad0581b34b4acd3f25b61d939ea5875fe7f4dc8ec0
digests-26890695543-ghcr.io-ls1intum-module-management-server-linux-arm64 Expired
244 Bytes
sha256:245eabc3ea6f6a5545866748a16b71b09d96ace39479891c5ff281f445869fd1
ls1intum~Module-Management~D02H2T.dockerbuild Expired
77.2 KB
sha256:ba84fd89d3e06c10e1d82f6996c47fb631a337218089c683ad49363df8a91be6
ls1intum~Module-Management~NWLGJZ.dockerbuild Expired
75.8 KB
sha256:fe824a723778dc5295984ebb25f5afea2feabb40a56a9f4e53af33f217005c7a
ls1intum~Module-Management~WQ3C2U.dockerbuild Expired
27.7 KB
sha256:a87d2764dfe0bc9a86b9f1e4d355b8274c51ed7f3da370e00c0092c0a96f0b97