Skip to content

changelogs, versionings #207

changelogs, versionings

changelogs, versionings #207

Triggered via push June 4, 2026 10:53
Status Failure
Total duration 2m 19s
Artifacts

build-test.yml

on: push
Matrix: Lint, Build and test
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 2 warnings
Lint, Build and test (24.x)
Process completed with exit code 1.
[Frontend] frontend/src/pages/services/stack-actions-menu.spec.tsx: frontend/src/pages/services/stack-actions-menu.tsx#L6
Error: [vitest] There was an error when mocking a module. If you are using "vi.mock" factory, make sure there are no top level variables inside, since this call is hoisted to top of the file. Read more: https://vitest.dev/api/vi.html#vi-mock ❯ frontend/src/pages/services/stack-actions-menu.tsx:6:1 Caused by: Caused by: ReferenceError: Cannot access 'stackCraftNavigate' before initialization ❯ frontend/src/pages/services/stack-actions-menu.spec.tsx:12:3
[Frontend] frontend/src/components/stack-redirect.spec.tsx > StackRedirect > should replace location with the stack services route on mount: frontend/src/components/stack-redirect.spec.tsx#L37
AssertionError: expected "vi.fn()" to be called with arguments: [ Array(2) ] Number of calls: 0 ❯ frontend/src/components/stack-redirect.spec.tsx:37:31
[Frontend] frontend/src/components/service-table.spec.tsx > ServiceTable > should render primary, logs, and details actions only: frontend/src/components/service-table.spec.tsx#L73
AssertionError: expected [] to include 'Start' ❯ frontend/src/components/service-table.spec.tsx:73:20
Lint, Build and test (26.x)
The strategy configuration was canceled because "build._24_x" failed
Lint, Build and test (26.x)
The operation was canceled.
[Frontend] frontend/src/pages/services/stack-actions-menu.spec.tsx: frontend/src/pages/services/stack-actions-menu.tsx#L6
Error: [vitest] There was an error when mocking a module. If you are using "vi.mock" factory, make sure there are no top level variables inside, since this call is hoisted to top of the file. Read more: https://vitest.dev/api/vi.html#vi-mock ❯ frontend/src/pages/services/stack-actions-menu.tsx:6:1 Caused by: Caused by: ReferenceError: Cannot access 'stackCraftNavigate' before initialization ❯ frontend/src/pages/services/stack-actions-menu.spec.tsx:12:3
[Frontend] frontend/src/components/stack-redirect.spec.tsx > StackRedirect > should replace location with the stack services route on mount: frontend/src/components/stack-redirect.spec.tsx#L37
AssertionError: expected "vi.fn()" to be called with arguments: [ Array(2) ] Number of calls: 0 ❯ frontend/src/components/stack-redirect.spec.tsx:37:31
[Frontend] frontend/src/components/service-table.spec.tsx > ServiceTable > should render primary, logs, and details actions only: frontend/src/components/service-table.spec.tsx#L73
AssertionError: expected [] to include 'Start' ❯ frontend/src/components/service-table.spec.tsx:73:20
Lint, Build and test (24.x)
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/setup-node@v4. 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/
Lint, Build and test (26.x)
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/setup-node@v4. 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/