vitest-ecosystem-ci #413
Annotations
18 errors and 21 warnings
|
test-ecosystem (vitest-vscode)
Process completed with exit code 1.
|
|
test-ecosystem (elk)
Process completed with exit code 1.
|
|
test-ecosystem (vitest-in-webcontainer)
Process completed with exit code 1.
|
|
[chromium] test/basic.test.ts > run tests:
workspace/vitest-in-webcontainer/vitest-in-webcontainer/test/basic.test.ts#L12
AssertionError: expected '> test\r\n> vitest run\r\n\r\n[rolldo…' to contain '✓ test/math.test.ts'
- Expected
+ Received
- ✓ test/math.test.ts
+ > test
+ > vitest run
+
+ [rolldown] Downloading @rolldown/binding-wasm32-wasi@1.0.0-rc.10 on WebContainer...
+ Progress: resolved 1, reused 0, downloaded 0, added 0
+ Progress: resolved 2, reused 0, downloaded 0, added 0
+ Packages: +7
+ +++++++
+ Progress: resolved 2, reused 0, downloaded 0, added 0
+ Progress: resolved 7, reused 0, downloaded 0, added 0
+ Progress: resolved 7, reused 0, downloaded 1, added 0
+ Progress: resolved 7, reused 0, downloaded 1, added 1
+ Progress: resolved 7, reused 0, downloaded 2, added 2
+ Progress: resolved 7, reused 0, downloaded 3, added 3
+ Progress: resolved 7, reused 0, downloaded 4, added 4
+ Progress: resolved 7, reused 0, downloaded 5, added 5
+ Progress: resolved 7, reused 0, downloaded 6, added 6
+ Progress: resolved 7, reused 0, downloaded 7, added 7, done
+
+ dependencies:
+ + @rolldown/binding-wasm32-wasi 1.0.0-rc.10
+
+ Done in 3.4s
+ (node:10) ExperimentalWarning: WASI is an experimental feature and might change at any time
+ (Use `node --trace-warnings ...` to show where the warning was created)
+ (node:10) ExperimentalWarning: WASI is an experimental feature and might change at any time
+ (Use `node --trace-warnings ...` to show where the warning was created)
+
+ RUN v4.1.0 /home/7ofir345m6q6633tpeiuc2qyfkn8px-czlf
+
+
+ ❯ test/math.test.ts [queued]
+
+ Test Files 0 passed (1)
+ Tests 0 passed (0)
+ Start at 06:13:34
+ Duration 704ms
+ ❯ test/math.test.ts (0 test)
+
+ ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Suites 1 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
+
+ FAIL test/math.test.ts [ test/math.test.ts ]
+ Error: Cannot read properties of undefined (reading 'whenLoaded')
+ ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯
+
+
+ Test Files 1 failed (1)
+ Tests no tests
+ Start at 06:13:34
+ Duration 808ms (transform 0ms, setup 0ms, import 0ms, tests 0ms, environment 0ms)
+
+ \
❯ test/basic.test.ts:12:17
|
|
[chromium] test/basic.test.ts > run tests:
workspace/vitest-in-webcontainer/vitest-in-webcontainer/test/basic.test.ts#L12
AssertionError: expected '> test\r\n> vitest run\r\n\r\n[rolldo…' to contain '✓ test/math.test.ts'
- Expected
+ Received
- ✓ test/math.test.ts
+ > test
+ > vitest run
+
+ [rolldown] Downloading @rolldown/binding-wasm32-wasi@1.0.0-rc.10 on WebContainer...
+ Progress: resolved 1, reused 0, downloaded 0, added 0
+ Progress: resolved 2, reused 0, downloaded 0, added 0
+ Packages: +7
+ +++++++
+ Progress: resolved 2, reused 0, downloaded 0, added 0
+ Progress: resolved 7, reused 0, downloaded 0, added 0
+ Progress: resolved 7, reused 0, downloaded 1, added 0
+ Progress: resolved 7, reused 0, downloaded 1, added 1
+ Progress: resolved 7, reused 0, downloaded 2, added 2
+ Progress: resolved 7, reused 0, downloaded 3, added 3
+ Progress: resolved 7, reused 0, downloaded 4, added 4
+ Progress: resolved 7, reused 0, downloaded 5, added 5
+ Progress: resolved 7, reused 0, downloaded 6, added 6
+ Progress: resolved 7, reused 0, downloaded 7, added 7, done
+
+ dependencies:
+ + @rolldown/binding-wasm32-wasi 1.0.0-rc.10
+
+ Done in 3.4s
+ (node:10) ExperimentalWarning: WASI is an experimental feature and might change at any time
+ (Use `node --trace-warnings ...` to show where the warning was created)
+ (node:10) ExperimentalWarning: WASI is an experimental feature and might change at any time
+ (Use `node --trace-warnings ...` to show where the warning was created)
+
+ RUN v4.1.0 /home/7ofir345m6q6633tpeiuc2qyfkn8px-czlf
+
+
+ ❯ test/math.test.ts [queued]
+
+ Test Files 0 passed (1)
+ Tests 0 passed (0)
+ Start at 06:13:34
+ Duration 704ms
+ ❯ test/math.test.ts (0 test)
+
+ ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Suites 1 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
+
+ FAIL test/math.test.ts [ test/math.test.ts ]
+ Error: Cannot read properties of undefined (reading 'whenLoaded')
+ ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯
+
+
+ Test Files 1 failed (1)
+ Tests no tests
+ Start at 06:13:34
+ Duration 808ms (transform 0ms, setup 0ms, import 0ms, tests 0ms, environment 0ms)
+
+ \
❯ test/basic.test.ts:12:17
|
|
test-ecosystem (hono)
Process completed with exit code 1.
|
|
test-ecosystem (webcontainer-test)
Process completed with exit code 1.
|
|
test-ecosystem (nuxt-test-utils)
Process completed with exit code 1.
|
|
packages/platform-browser/test/KeyValueStore.test.ts > KeyValueStore / layerLocalStorage > clear:
workspace/effect/effect/packages/platform-browser/src/internal/keyValueStore.ts#L7
(FiberFailure) ReferenceError: localStorage is not defined
❯ packages/platform-browser/src/internal/keyValueStore.ts:7:67
❯ packages/platform/src/internal/keyValueStore.ts:260:21
❯ packages/effect/src/internal/layer.ts:1035:62
❯ packages/effect/src/internal/fiberRuntime.ts:1161:41
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { _id: 'FiberFailure' }
|
|
packages/platform-browser/test/KeyValueStore.test.ts > KeyValueStore / layerLocalStorage > remove:
workspace/effect/effect/packages/platform-browser/src/internal/keyValueStore.ts#L7
(FiberFailure) ReferenceError: localStorage is not defined
❯ packages/platform-browser/src/internal/keyValueStore.ts:7:67
❯ packages/platform/src/internal/keyValueStore.ts:260:21
❯ packages/effect/src/internal/layer.ts:1035:62
❯ packages/effect/src/internal/fiberRuntime.ts:1161:41
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { _id: 'FiberFailure' }
|
|
packages/platform-browser/test/KeyValueStore.test.ts > KeyValueStore / layerLocalStorage > remove:
workspace/effect/effect/packages/platform-browser/src/internal/keyValueStore.ts#L7
(FiberFailure) ReferenceError: localStorage is not defined
❯ packages/platform-browser/src/internal/keyValueStore.ts:7:67
❯ packages/platform/src/internal/keyValueStore.ts:260:21
❯ packages/effect/src/internal/layer.ts:1035:62
❯ packages/effect/src/internal/fiberRuntime.ts:1161:41
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { _id: 'FiberFailure' }
|
|
packages/platform-browser/test/KeyValueStore.test.ts > KeyValueStore / layerLocalStorage > get/ missing:
workspace/effect/effect/packages/platform-browser/src/internal/keyValueStore.ts#L7
(FiberFailure) ReferenceError: localStorage is not defined
❯ packages/platform-browser/src/internal/keyValueStore.ts:7:67
❯ packages/platform/src/internal/keyValueStore.ts:260:21
❯ packages/effect/src/internal/layer.ts:1035:62
❯ packages/effect/src/internal/fiberRuntime.ts:1161:41
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { _id: 'FiberFailure' }
|
|
packages/platform-browser/test/KeyValueStore.test.ts > KeyValueStore / layerLocalStorage > get/ missing:
workspace/effect/effect/packages/platform-browser/src/internal/keyValueStore.ts#L7
(FiberFailure) ReferenceError: localStorage is not defined
❯ packages/platform-browser/src/internal/keyValueStore.ts:7:67
❯ packages/platform/src/internal/keyValueStore.ts:260:21
❯ packages/effect/src/internal/layer.ts:1035:62
❯ packages/effect/src/internal/fiberRuntime.ts:1161:41
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { _id: 'FiberFailure' }
|
|
packages/platform-browser/test/KeyValueStore.test.ts > KeyValueStore / layerLocalStorage > set:
workspace/effect/effect/packages/platform-browser/src/internal/keyValueStore.ts#L7
(FiberFailure) ReferenceError: localStorage is not defined
❯ packages/platform-browser/src/internal/keyValueStore.ts:7:67
❯ packages/platform/src/internal/keyValueStore.ts:260:21
❯ packages/effect/src/internal/layer.ts:1035:62
❯ packages/effect/src/internal/fiberRuntime.ts:1161:41
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { _id: 'FiberFailure' }
|
|
packages/platform-browser/test/KeyValueStore.test.ts > KeyValueStore / layerLocalStorage > set:
workspace/effect/effect/packages/platform-browser/src/internal/keyValueStore.ts#L7
(FiberFailure) ReferenceError: localStorage is not defined
❯ packages/platform-browser/src/internal/keyValueStore.ts:7:67
❯ packages/platform/src/internal/keyValueStore.ts:260:21
❯ packages/effect/src/internal/layer.ts:1035:62
❯ packages/effect/src/internal/fiberRuntime.ts:1161:41
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { _id: 'FiberFailure' }
|
|
packages/effect/test/assertions.test.ts > expect > Cause > sequential vs parallel > toStrictEqual:
workspace/effect/effect/packages/effect/test/assertions.test.ts#L64
AssertionError: expected { _id: 'Cause', …(3) } to strictly equal { Object (_tag, left, ...) }
- Expected
+ Received
@@ -1,8 +1,8 @@
{
"_id": "Cause",
- "_tag": "Parallel",
+ "_tag": "Sequential",
"left": {
"_id": "Cause",
"_tag": "Empty",
},
"right": {
❯ packages/effect/test/assertions.test.ts:64:60
|
|
packages/effect/test/assertions.test.ts > expect > Cause > sequential vs parallel > toEqual:
workspace/effect/effect/packages/effect/test/assertions.test.ts#L60
AssertionError: expected { _id: 'Cause', …(3) } to deeply equal { Object (_tag, left, ...) }
- Expected
+ Received
@@ -1,8 +1,8 @@
{
"_id": "Cause",
- "_tag": "Parallel",
+ "_tag": "Sequential",
"left": {
"_id": "Cause",
"_tag": "Empty",
},
"right": {
❯ packages/effect/test/assertions.test.ts:60:60
|
|
scripts/codemods/ts-fence.test.ts:
workspace/effect/effect/scripts/codemods/ts-fence.test.ts#L13
ReferenceError: it is not defined
❯ Proxy.defineInlineTest node_modules/.pnpm/jscodeshift@17.3.0/node_modules/jscodeshift/src/testUtils.js:143:3
❯ scripts/codemods/ts-fence.test.ts:13:13
❯ scripts/codemods/ts-fence.test.ts:24:1
|
|
test-ecosystem (vitest-sonar-reporter)
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 2nd, 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/
|
|
test-ecosystem (vitest-pool-example)
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 2nd, 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/
|
|
test-ecosystem (vitest-vscode)
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 2nd, 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/
|
|
test-ecosystem (elk)
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 2nd, 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/
|
|
test-ecosystem (zustand)
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 2nd, 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/
|
|
test-ecosystem (vitest-reporters-large)
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 2nd, 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/
|
|
test-ecosystem (aria-live-capture)
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 2nd, 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/
|
|
test-ecosystem (vitest-browser-examples)
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 2nd, 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/
|
|
test-ecosystem (sveltejs-cli)
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 2nd, 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/
|
|
test-ecosystem (vite)
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 2nd, 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/
|
|
test-ecosystem (vitest-in-webcontainer)
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 2nd, 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/
|
|
test-ecosystem (lerna-lite)
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 2nd, 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/
|
|
test-ecosystem (vue)
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 2nd, 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/
|
|
test-ecosystem (hono)
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 2nd, 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/
|
|
test-ecosystem (webcontainer-test)
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 2nd, 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/
|
|
test-ecosystem (vitest-pool-workers)
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 2nd, 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/
|
|
test-ecosystem (nuxt-test-utils)
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 2nd, 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/
|
|
test-ecosystem (nuxt)
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 2nd, 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/
|
|
test-ecosystem (vitest-benchmark-large)
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 2nd, 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/
|
|
test-ecosystem (effect)
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 2nd, 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/
|
|
test-ecosystem (vitest-coverage-large)
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 2nd, 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/
|