Skip to content

chore(deps): update dependency vitest to v4 #1177

chore(deps): update dependency vitest to v4

chore(deps): update dependency vitest to v4 #1177

Triggered via pull request June 15, 2026 13:15
Status Failure
Total duration 1m 5s
Artifacts

continuous-delivery.yml

on: pull_request
Publish Acryss image to container registries
58s
Publish Acryss image to container registries
Publish Nayre image to container registries
53s
Publish Nayre image to container registries
Publish Frontend image to container registries
50s
Publish Frontend image to container registries
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
Publish Frontend image to container registries
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c yarn install --immutable" did not complete successfully: exit code: 1
Publish Acryss image to container registries
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c yarn install --immutable" did not complete successfully: exit code: 1
Publish Nayre image to container registries
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c yarn install --immutable" did not complete successfully: exit code: 1
Publish Frontend image to container registries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5.1.0, docker/login-action@v3.0.0, docker/setup-buildx-action@v3.1.0. 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/
Publish Acryss image to container registries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5.1.0, docker/login-action@v3.0.0, docker/setup-buildx-action@v3.1.0. 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/
Publish Nayre image to container registries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5.1.0, docker/login-action@v3.0.0, docker/setup-buildx-action@v3.1.0. 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/