Process completed with exit code 1.

Error: No tests found. Make sure that arguments are regular expressions matching test files. You may need to escape symbols like "$" or "*" and quote the arguments.

Error: Playwright Test did not expect test.describe() to be called here. Most common reasons include: - You are calling test.describe() in a configuration file. - You are calling test.describe() in a file that is imported by the configuration file. - You have two different versions of @playwright/test. This usually happens when one of the dependencies in your package.json depends on @playwright/test. - You are calling test.describe() from an async test.describe() block. Only sync ones are supported. at perf-stability.spec.ts:3 1 | import { test, expect } from '@playwright/test' 2 | > 3 | test.describe('WebSocket Stability', () => { | ^ 4 | test('should maintain a stable WebSocket connection', async ({ page }) => { 5 | test.setTimeout(40000) 6 | await page.goto('/') at _TestTypeImpl._currentSuite (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:2256:13) at _TestTypeImpl._describe (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:2297:24) at Function.describe (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:1219:12) at /home/runner/work/hrm/hrm/tests/playwright/perf-stability.spec.ts:3:6

Error: Playwright Test did not expect test.describe() to be called here. Most common reasons include: - You are calling test.describe() in a configuration file. - You are calling test.describe() in a file that is imported by the configuration file. - You have two different versions of @playwright/test. This usually happens when one of the dependencies in your package.json depends on @playwright/test. - You are calling test.describe() from an async test.describe() block. Only sync ones are supported. at perf-memory.spec.ts:17 15 | const HEAP_GROWTH_THRESHOLD = 0.35 // 35% (relaxed further to account for sandbox/CI variance) 16 | > 17 | test.describe('Frontend Performance', () => { | ^ 18 | test('should not exhibit memory leaks during a simulated workout', async ({ 19 | page, 20 | }) => { at _TestTypeImpl._currentSuite (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:2256:13) at _TestTypeImpl._describe (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:2297:24) at Function.describe (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:1219:12) at /home/runner/work/hrm/hrm/tests/playwright/perf-memory.spec.ts:17:6

Error: Playwright Test did not expect test.describe() to be called here. Most common reasons include: - You are calling test.describe() in a configuration file. - You are calling test.describe() in a file that is imported by the configuration file. - You have two different versions of @playwright/test. This usually happens when one of the dependencies in your package.json depends on @playwright/test. - You are calling test.describe() from an async test.describe() block. Only sync ones are supported. at perf-load.spec.ts:4 2 | import { waitForPageReady } from './lib/waits' 3 | > 4 | test.describe('Dashboard Load Performance', () => { | ^ 5 | test('should load within acceptable threshold', async ({ page }) => { 6 | const start = performance.now() 7 | await page.goto('/') at _TestTypeImpl._currentSuite (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:2256:13) at _TestTypeImpl._describe (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:2297:24) at Function.describe (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:1219:12) at /home/runner/work/hrm/hrm/tests/playwright/perf-load.spec.ts:4:6

Error: Playwright Test did not expect test.describe.configure() to be called here. Most common reasons include: - You are calling test.describe.configure() in a configuration file. - You are calling test.describe.configure() in a file that is imported by the configuration file. - You have two different versions of @playwright/test. This usually happens when one of the dependencies in your package.json depends on @playwright/test. - You are calling test.describe.configure() from an async test.describe() block. Only sync ones are supported. at vrt-spotify-controls.spec.ts:8 6 | 7 | // Test suite configuration > 8 | test.describe.configure({ mode: 'serial' }) | ^ 9 | 10 | // Reusable page objects 11 | let controlPage: Page at _TestTypeImpl._currentSuite (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:2256:13) at _TestTypeImpl._configure (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:2353:24) at Function.configure (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:1219:12) at /home/runner/work/hrm/hrm/tests/playwright/vrt-spotify-controls.spec.ts:8:15

Error: Playwright Test did not expect test.describe.configure() to be called here. Most common reasons include: - You are calling test.describe.configure() in a configuration file. - You are calling test.describe.configure() in a file that is imported by the configuration file. - You have two different versions of @playwright/test. This usually happens when one of the dependencies in your package.json depends on @playwright/test. - You are calling test.describe.configure() from an async test.describe() block. Only sync ones are supported. at vrt-mock-hrm-client.spec.ts:8 6 | 7 | // Test suite configuration > 8 | test.describe.configure({ mode: 'serial' }) | ^ 9 | 10 | // Reusable page objects 11 | let mockPage: Page at _TestTypeImpl._currentSuite (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:2256:13) at _TestTypeImpl._configure (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:2353:24) at Function.configure (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:1219:12) at /home/runner/work/hrm/hrm/tests/playwright/vrt-mock-hrm-client.spec.ts:8:15

Error: Playwright Test did not expect test.describe.configure() to be called here. Most common reasons include: - You are calling test.describe.configure() in a configuration file. - You are calling test.describe.configure() in a file that is imported by the configuration file. - You have two different versions of @playwright/test. This usually happens when one of the dependencies in your package.json depends on @playwright/test. - You are calling test.describe.configure() from an async test.describe() block. Only sync ones are supported. at vrt-hr-components.spec.ts:15 13 | 14 | // Test suite configuration > 15 | test.describe.configure({ mode: 'serial' }) | ^ 16 | 17 | // Reusable page objects 18 | let dashboardPage: Page at _TestTypeImpl._currentSuite (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:2256:13) at _TestTypeImpl._configure (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:2353:24) at Function.configure (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:1219:12) at /home/runner/work/hrm/hrm/tests/playwright/vrt-hr-components.spec.ts:15:15

Error: Playwright Test did not expect test.describe() to be called here. Most common reasons include: - You are calling test.describe() in a configuration file. - You are calling test.describe() in a file that is imported by the configuration file. - You have two different versions of @playwright/test. This usually happens when one of the dependencies in your package.json depends on @playwright/test. - You are calling test.describe() from an async test.describe() block. Only sync ones are supported. at vrt-experimental.spec.ts:6 4 | import { waitForPageReady } from './lib/waits' 5 | > 6 | test.describe('Experimental Analytics Page VRT', () => { | ^ 7 | test('initial state', async ({ dashboardPage }) => { 8 | await setupMinimalVisualRegressionTest( 9 | dashboardPage, at _TestTypeImpl._currentSuite (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:2256:13) at _TestTypeImpl._describe (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:2297:24) at Function.describe (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:1219:12) at /home/runner/work/hrm/hrm/tests/playwright/vrt-experimental.spec.ts:6:6

Error: Playwright Test did not expect test.describe() to be called here. Most common reasons include: - You are calling test.describe() in a configuration file. - You are calling test.describe() in a file that is imported by the configuration file. - You have two different versions of @playwright/test. This usually happens when one of the dependencies in your package.json depends on @playwright/test. - You are calling test.describe() from an async test.describe() block. Only sync ones are supported. at vrt-dashboard.spec.ts:13 11 | 12 | // Test suite for VRT > 13 | test.describe('Dashboard Visual Regression Tests', () => { | ^ 14 | test.describe('Dashboard Component', () => { 15 | test('initial, empty state', async ({ dashboardPage }) => { 16 | await setupMinimalVisualRegressionTest(dashboardPage, '/') at _TestTypeImpl._currentSuite (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:2256:13) at _TestTypeImpl._describe (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:2297:24) at Function.describe (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:1219:12) at /home/runner/work/hrm/hrm/tests/playwright/vrt-dashboard.spec.ts:13:6

Error: Playwright Test did not expect test.describe.configure() to be called here. Most common reasons include: - You are calling test.describe.configure() in a configuration file. - You are calling test.describe.configure() in a file that is imported by the configuration file. - You have two different versions of @playwright/test. This usually happens when one of the dependencies in your package.json depends on @playwright/test. - You are calling test.describe.configure() from an async test.describe() block. Only sync ones are supported. at vrt-control-panel.spec.ts:8 6 | 7 | // Test suite configuration > 8 | test.describe.configure({ mode: 'serial' }) | ^ 9 | 10 | // Reusable page objects 11 | let controlPage: Page at _TestTypeImpl._currentSuite (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:2256:13) at _TestTypeImpl._configure (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:2353:24) at Function.configure (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:1219:12) at /home/runner/work/hrm/hrm/tests/playwright/vrt-control-panel.spec.ts:8:15

Error: Playwright Test did not expect test.describe() to be called here. Most common reasons include: - You are calling test.describe() in a configuration file. - You are calling test.describe() in a file that is imported by the configuration file. - You have two different versions of @playwright/test. This usually happens when one of the dependencies in your package.json depends on @playwright/test. - You are calling test.describe() from an async test.describe() block. Only sync ones are supported. at vrt-connect-page.spec.ts:9 7 | import { BluetoothConnectionStatus } from '../../types/bluetooth' 8 | > 9 | test.describe('Visual Regression Tests for /client/connect Page', () => { | ^ 10 | test.beforeEach(async ({ connectPage }) => { 11 | await injectBluetoothMocks(connectPage) 12 | await connectPage.goto('/client/connect') at _TestTypeImpl._currentSuite (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:2256:13) at _TestTypeImpl._describe (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:2297:24) at Function.describe (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:1219:12) at /home/runner/work/hrm/hrm/tests/playwright/vrt-connect-page.spec.ts:9:6

Error: Playwright Test did not expect test.describe() to be called here. Most common reasons include: - You are calling test.describe() in a configuration file. - You are calling test.describe() in a file that is imported by the configuration file. - You have two different versions of @playwright/test. This usually happens when one of the dependencies in your package.json depends on @playwright/test. - You are calling test.describe() from an async test.describe() block. Only sync ones are supported. at vrt-components.spec.ts:13 11 | import { VRT_TIMEOUTS } from './lib/timeouts' 12 | > 13 | test.describe('Component-Specific VRT', () => { | ^ 14 | test('BottomNavBar highlights correct icon', async ({ dashboardPage }) => { 15 | await setupMinimalVisualRegressionTest(dashboardPage, '/') 16 | const bottomNav = dashboardPage.getByTestId('bottom-nav-bar') at _TestTypeImpl._currentSuite (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:2256:13) at _TestTypeImpl._describe (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:2297:24) at Function.describe (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:1219:12) at /home/runner/work/hrm/hrm/tests/playwright/vrt-components.spec.ts:13:6

Error: Playwright Test did not expect test.describe() to be called here. Most common reasons include: - You are calling test.describe() in a configuration file. - You are calling test.describe() in a file that is imported by the configuration file. - You have two different versions of @playwright/test. This usually happens when one of the dependencies in your package.json depends on @playwright/test. - You are calling test.describe() from an async test.describe() block. Only sync ones are supported. at simple-smoke.spec.ts:5 3 | import { BASE_URL } from './lib' 4 | > 5 | test.describe('Simple Smoke Test', () => { | ^ 6 | test('should load the homepage and have the correct title', async ({ 7 | page, 8 | }) => { at _TestTypeImpl._currentSuite (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:2256:13) at _TestTypeImpl._describe (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:2297:24) at Function.describe (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:1219:12) at /home/runner/work/hrm/hrm/tests/playwright/simple-smoke.spec.ts:5:6

Error: Playwright Test did not expect test.describe() to be called here. Most common reasons include: - You are calling test.describe() in a configuration file. - You are calling test.describe() in a file that is imported by the configuration file. - You have two different versions of @playwright/test. This usually happens when one of the dependencies in your package.json depends on @playwright/test. - You are calling test.describe() from an async test.describe() block. Only sync ones are supported. at remote-capabilities.spec.ts:7 5 | const BASE_URL = getBaseURL() 6 | > 7 | test.describe('Remote Capabilities & Command Relay', () => { | ^ 8 | test('Controller sends commands via WebSocket', async ({ page }) => { 9 | // 1. Setup Network & WS capture 10 | const failedRequests: string[] = [] at _TestTypeImpl._currentSuite (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:2256:13) at _TestTypeImpl._describe (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:2297:24) at Function.describe (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:1219:12) at /home/runner/work/hrm/hrm/tests/playwright/remote-capabilities.spec.ts:7:6

Process completed with exit code 1.

Error: No tests found. Make sure that arguments are regular expressions matching test files. You may need to escape symbols like "$" or "*" and quote the arguments.

Error: Playwright Test did not expect test.describe() to be called here. Most common reasons include: - You are calling test.describe() in a configuration file. - You are calling test.describe() in a file that is imported by the configuration file. - You have two different versions of @playwright/test. This usually happens when one of the dependencies in your package.json depends on @playwright/test. - You are calling test.describe() from an async test.describe() block. Only sync ones are supported. at infrastructure.spec.ts:30 28 | } 29 | > 30 | test.describe('Infrastructure & Scripts', () => { | ^ 31 | // 1. LINT CHECK 32 | // Ensures you never commit code that violates ESLint rules. 33 | // Skipping since pnpm build is already running in ci at _TestTypeImpl._currentSuite (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:2256:13) at _TestTypeImpl._describe (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:2297:24) at Function.describe (/home/runner/work/hrm/hrm/node_modules/.pnpm/playwright@1.61.0/node_modules/playwright/lib/common/index.js:1219:12) at /home/runner/work/hrm/hrm/tests/playwright/infrastructure.spec.ts:30:6

No test report files were found

Process completed with exit code 1.

Error when evaluating 'secrets'. .github/workflows/pr-orchestrator.yml (Line: 248, Col: 11): Secret GEMINI_API_KEY is required, but not provided while calling., .github/workflows/pr-orchestrator.yml (Line: 248, Col: 11): Secret ARI_PAT is required, but not provided while calling.

Error when evaluating 'secrets'. .github/workflows/pr-orchestrator.yml (Line: 248, Col: 11): Secret GEMINI_API_KEY is required, but not provided while calling., .github/workflows/pr-orchestrator.yml (Line: 248, Col: 11): Secret ARI_PAT is required, but not provided while calling.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v7. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, dorny/paths-filter@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/

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-python@v5. 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/

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 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, dorny/test-reporter@v1, pnpm/action-setup@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, dorny/test-reporter@v1, pnpm/action-setup@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, dorny/test-reporter@v1, pnpm/action-setup@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, dorny/test-reporter@v1, pnpm/action-setup@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/

No file matches path test-results/component-results.xml

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, dorny/test-reporter@v1, pnpm/action-setup@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/

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 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/