Skip to content

fix(deps): update mui to v9 (major) #951

fix(deps): update mui to v9 (major)

fix(deps): update mui to v9 (major) #951

Triggered via pull request April 8, 2026 08:39
Status Failure
Total duration 59s
Artifacts 2

pr-open.yml

on: pull_request
Matrix: Builds
PR Greeting
6s
PR Greeting
Deploys  /  Helm
Deploys / Helm
Matrix: Tests / Cypress E2E
Waiting for pending jobs
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 4 warnings
Builds (frontend)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c npm ci --ignore-scripts && npm run build" did not complete successfully: exit code: 1
Builds (api)
The strategy configuration was canceled because "builds.frontend" failed
Builds (api)
The operation was canceled.
Builds (database)
The strategy configuration was canceled because "builds.frontend" failed
Builds (database)
The operation was canceled.
PR Greeting
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bcgov/action-pr-description-add@9bf88aec33edb7c00ed72f9305aa1721d0cdab9f. 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/
Builds (frontend)
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@v6, docker/login-action@v3, docker/setup-buildx-action@v3. 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/
Builds (api)
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@v6, docker/login-action@v3, docker/setup-buildx-action@v3. 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/
Builds (database)
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@v6, docker/login-action@v3, docker/setup-buildx-action@v3. 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
bcgov~pubcode~7384NX.dockerbuild
33.4 KB
sha256:0c86ba6978bff17cd6dd0dfd6474c4923eab4c830920c2ba565f46b9b68b471d
bcgov~pubcode~QOWLIR.dockerbuild
26.3 KB
sha256:13fc464593efb45fd96f1edfa705c66c2274dbf0a7e79a66968057bae3820fd9