[docs] add "Patterns" tab with installable Workflow patterns #9624
tests.yml
on: pull_request
Get Test Matrix
10s
Matrix: e2e-vercel-prod
E2E Windows Tests
4m 15s
Matrix: unit
Get Community Worlds Matrix
0s
Create PR Comment
6s
Node.js Module Build Errors Test
2m 51s
Vitest Plugin Tests
2m 15s
Matrix: e2e-local-dev
Matrix: e2e-local-postgres
Matrix: e2e-local-prod
Matrix: e2e-community
Waiting for pending jobs
E2E Required Check
2s
Publish E2E Results
0s
Annotations
107 errors and 57 warnings
|
E2E Local Prod Tests (nextjs-webpack - stable)
Process completed with exit code 1.
|
|
packages/core/e2e/local-build.test.ts > e2e > builds without errors:
packages/core/e2e/local-build.test.ts#L54
Error: Command "pnpm build" failed with exit code 1
> nextjs-webpack@0.0.2-alpha.5 prebuild /tmp/workflow-nextjs-webpack-AVg8gT/workbench/nextjs-webpack
> pnpm generate:workflows
> nextjs-webpack@0.0.2-alpha.5 generate:workflows /tmp/workflow-nextjs-webpack-AVg8gT/workbench/nextjs-webpack
> node ../scripts/generate-workflows-registry.js
✓ Generated ./_workflows.ts with 15 workflow(s)
- workflows/100_durable_agent_e2e.ts
- workflows/10_single_stmt_control_flow.ts
- workflows/1_simple.ts
- workflows/2_control_flow.ts
- workflows/3_streams.ts
- workflows/4_ai.ts
- workflows/5_hooks.ts
- workflows/6_batching.ts
- workflows/7_full.ts
- workflows/8_react_render.tsx
- workflows/98_duplicate_case.ts
- workflows/99_e2e.ts
- workflows/agent_chat.ts
- workflows/serde-models.ts
- workflows/serde-steps.ts
> nextjs-webpack@0.0.2-alpha.5 build /tmp/workflow-nextjs-webpack-AVg8gT/workbench/nextjs-webpack
> next build --webpack
Attention: Next.js now collects completely anonymous telemetry regarding usage.
This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry
▲ Next.js 16.2.1 (webpack)
- Experiments (use with caution):
· deferredEntries
· onBeforeDeferredEntries
⨯ serverMinification
Creating an optimized production build ...
Failed to compile.
./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node
Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
Import trace for requested module:
./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node
./node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js
./node_modules/.pnpm/@vercel+cli-auth@0.1.0/node_modules/@vercel/cli-auth/credentials-store.js
./node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/auth-config.js
./node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/token-util.js
./node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/index.js
./node_modules/.pnpm/@vercel+queue@0.1.4/node_modules/@vercel/queue/dist/index.mjs
./node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/queue.js
./node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/index.js
./node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime/world.js
./node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime.js
./node_modules/.pnpm/workflow@file+..+..+tarballs+workflow-5.0.0-beta.2.tgz_@nestjs+common@11.1.19_reflect-m_b69e931b2c51a2a5cba5d083f6730fe9/node_modules/workflow/dist/runtime.js
./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node
Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
Import trace for requested module:
./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node
./node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js
./node_modules/.pnpm/@vercel+cli-auth@0.1.0/node_modu
|
|
E2E Local Prod Tests (nextjs-webpack - canary)
Process completed with exit code 1.
|
|
packages/core/e2e/local-build.test.ts > e2e > builds without errors:
packages/core/e2e/local-build.test.ts#L54
Error: Command "pnpm build" failed with exit code 1
> nextjs-webpack@0.0.2-alpha.5 prebuild /tmp/workflow-nextjs-webpack-qqmQsQ/workbench/nextjs-webpack
> pnpm generate:workflows
> nextjs-webpack@0.0.2-alpha.5 generate:workflows /tmp/workflow-nextjs-webpack-qqmQsQ/workbench/nextjs-webpack
> node ../scripts/generate-workflows-registry.js
✓ Generated ./_workflows.ts with 15 workflow(s)
- workflows/100_durable_agent_e2e.ts
- workflows/10_single_stmt_control_flow.ts
- workflows/1_simple.ts
- workflows/2_control_flow.ts
- workflows/3_streams.ts
- workflows/4_ai.ts
- workflows/5_hooks.ts
- workflows/6_batching.ts
- workflows/7_full.ts
- workflows/8_react_render.tsx
- workflows/98_duplicate_case.ts
- workflows/99_e2e.ts
- workflows/agent_chat.ts
- workflows/serde-models.ts
- workflows/serde-steps.ts
> nextjs-webpack@0.0.2-alpha.5 build /tmp/workflow-nextjs-webpack-qqmQsQ/workbench/nextjs-webpack
> next build --webpack
Attention: Next.js now collects completely anonymous telemetry regarding usage.
This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry
▲ Next.js 16.3.0-canary.2 (webpack)
- Experiments (use with caution):
· deferredEntries
· onBeforeDeferredEntries
⨯ serverMinification
Creating an optimized production build ...
Failed to compile.
./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node
Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
Import trace for requested module:
./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node
./node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js
./node_modules/.pnpm/@vercel+cli-auth@0.1.0/node_modules/@vercel/cli-auth/credentials-store.js
./node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/auth-config.js
./node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/token-util.js
./node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/index.js
./node_modules/.pnpm/@vercel+queue@0.1.4/node_modules/@vercel/queue/dist/index.mjs
./node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/queue.js
./node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/index.js
./node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime/world.js
./node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime.js
./node_modules/.pnpm/workflow@file+..+..+tarballs+workflow-5.0.0-beta.2.tgz_@nestjs+common@11.1.19_reflect-m_4c42f3f5f9f5fc457ff30c948191b6a5/node_modules/workflow/dist/runtime.js
./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node
Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
Import trace for requested module:
./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node
./node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js
./node_modules/.pnpm/@vercel+cli-auth@0.1.0/
|
|
E2E Local Prod Tests (nextjs-turbopack - canary)
Process completed with exit code 1.
|
|
packages/core/e2e/local-build.test.ts > e2e > builds without errors:
packages/core/e2e/local-build.test.ts#L54
Error: Command "pnpm build" failed with exit code 1
> nextjs-turbopack@0.0.2-alpha.5 prebuild /tmp/workflow-nextjs-turbopack-e2UI4V/workbench/nextjs-turbopack
> pnpm generate:workflows
> nextjs-turbopack@0.0.2-alpha.5 generate:workflows /tmp/workflow-nextjs-turbopack-e2UI4V/workbench/nextjs-turbopack
> node ../scripts/generate-workflows-registry.js
✓ Generated ./_workflows.ts with 19 workflow(s)
- workflows/100_durable_agent_e2e.ts
- workflows/10_single_stmt_control_flow.ts
- workflows/1_simple.ts
- workflows/2_control_flow.ts
- workflows/3_streams.ts
- workflows/4_ai.ts
- workflows/5_hooks.ts
- workflows/6_batching.ts
- workflows/7_full.ts
- workflows/8_react_render.tsx
- workflows/96_many_steps.ts
- workflows/97_bench.ts
- workflows/98_duplicate_case.ts
- workflows/99_e2e.ts
- workflows/agent_chat.ts
- workflows/serde-models.ts
- workflows/serde-steps.ts
- workflows/server_action_step_import_helpers.ts
- workflows/server_action_step_imports.ts
> nextjs-turbopack@0.0.2-alpha.5 build /tmp/workflow-nextjs-turbopack-e2UI4V/workbench/nextjs-turbopack
> next build --turbopack
Attention: Next.js now collects completely anonymous telemetry regarding usage.
This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry
▲ Next.js 16.3.0-canary.2 (Turbopack)
- Experiments (use with caution):
· deferredEntries
· onBeforeDeferredEntries
Creating an optimized production build ...
> Build error occurred
Error: Turbopack build failed with 2 errors:
./workbench/nextjs-turbopack/node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js
non-ecmascript placeable asset
asset is not placeable in ESM chunks, so it doesn't have a module id
Import traces:
App Route:
./workbench/nextjs-turbopack/node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+cli-auth@0.1.0/node_modules/@vercel/cli-auth/credentials-store.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/auth-config.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/token-util.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/index.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+queue@0.1.4/node_modules/@vercel/queue/dist/index.mjs
./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/queue.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/index.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime/world.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime/run.js
./workbench/nextjs-turbopack/app/api/chat/[runId]/stream/route.ts
Instrumentation:
./workbench/nextjs-turbopack/node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+cli-auth@0.1.0/node_modules/@vercel/cli-auth/credentials-store.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/auth-config.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/token-util.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/d
|
|
E2E Local Prod Tests (nextjs-turbopack - stable)
Process completed with exit code 1.
|
|
packages/core/e2e/local-build.test.ts > e2e > builds without errors:
packages/core/e2e/local-build.test.ts#L54
Error: Command "pnpm build" failed with exit code 1
> nextjs-turbopack@0.0.2-alpha.5 prebuild /tmp/workflow-nextjs-turbopack-zJkHrW/workbench/nextjs-turbopack
> pnpm generate:workflows
> nextjs-turbopack@0.0.2-alpha.5 generate:workflows /tmp/workflow-nextjs-turbopack-zJkHrW/workbench/nextjs-turbopack
> node ../scripts/generate-workflows-registry.js
✓ Generated ./_workflows.ts with 19 workflow(s)
- workflows/100_durable_agent_e2e.ts
- workflows/10_single_stmt_control_flow.ts
- workflows/1_simple.ts
- workflows/2_control_flow.ts
- workflows/3_streams.ts
- workflows/4_ai.ts
- workflows/5_hooks.ts
- workflows/6_batching.ts
- workflows/7_full.ts
- workflows/8_react_render.tsx
- workflows/96_many_steps.ts
- workflows/97_bench.ts
- workflows/98_duplicate_case.ts
- workflows/99_e2e.ts
- workflows/agent_chat.ts
- workflows/serde-models.ts
- workflows/serde-steps.ts
- workflows/server_action_step_import_helpers.ts
- workflows/server_action_step_imports.ts
> nextjs-turbopack@0.0.2-alpha.5 build /tmp/workflow-nextjs-turbopack-zJkHrW/workbench/nextjs-turbopack
> next build --turbopack
Attention: Next.js now collects completely anonymous telemetry regarding usage.
This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry
▲ Next.js 16.2.1 (Turbopack)
- Experiments (use with caution):
· deferredEntries
· onBeforeDeferredEntries
Creating an optimized production build ...
> Build error occurred
Error: Turbopack build failed with 2 errors:
./workbench/nextjs-turbopack/node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js
non-ecmascript placeable asset
asset is not placeable in ESM chunks, so it doesn't have a module id
Import traces:
App Route:
./workbench/nextjs-turbopack/node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+cli-auth@0.1.0/node_modules/@vercel/cli-auth/credentials-store.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/auth-config.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/token-util.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/index.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+queue@0.1.4/node_modules/@vercel/queue/dist/index.mjs
./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/queue.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/index.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime/world.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime/run.js
./workbench/nextjs-turbopack/app/api/chat/[runId]/stream/route.ts
Instrumentation:
./workbench/nextjs-turbopack/node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+cli-auth@0.1.0/node_modules/@vercel/cli-auth/credentials-store.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/auth-config.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/token-util.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/index
|
|
Unit Tests (windows-latest)
Process completed with exit code 1.
|
|
Unit Tests (windows-latest)
@workflow/utils#test: command (D:\a\workflow\workflow\packages\utils) C:\Users\runneradmin\setup-pnpm\node_modules\.bin\pnpm.CMD run test exited (1)
|
|
src/get-port.test.ts > getWorkflowPort > should respect custom timeout:
packages/utils/src/get-port.test.ts#L328
AssertionError: expected 2093 to be less than 2000
❯ src/get-port.test.ts:328:21
|
|
E2E Local Postgres Tests (nextjs-webpack - stable)
Process completed with exit code 1.
|
|
packages/core/e2e/local-build.test.ts > e2e > builds without errors:
packages/core/e2e/local-build.test.ts#L54
Error: Command "pnpm build" failed with exit code 1
> nextjs-webpack@0.0.2-alpha.5 prebuild /tmp/workflow-nextjs-webpack-mWjnPo/workbench/nextjs-webpack
> pnpm generate:workflows
> nextjs-webpack@0.0.2-alpha.5 generate:workflows /tmp/workflow-nextjs-webpack-mWjnPo/workbench/nextjs-webpack
> node ../scripts/generate-workflows-registry.js
✓ Generated ./_workflows.ts with 15 workflow(s)
- workflows/100_durable_agent_e2e.ts
- workflows/10_single_stmt_control_flow.ts
- workflows/1_simple.ts
- workflows/2_control_flow.ts
- workflows/3_streams.ts
- workflows/4_ai.ts
- workflows/5_hooks.ts
- workflows/6_batching.ts
- workflows/7_full.ts
- workflows/8_react_render.tsx
- workflows/98_duplicate_case.ts
- workflows/99_e2e.ts
- workflows/agent_chat.ts
- workflows/serde-models.ts
- workflows/serde-steps.ts
> nextjs-webpack@0.0.2-alpha.5 build /tmp/workflow-nextjs-webpack-mWjnPo/workbench/nextjs-webpack
> next build --webpack
Attention: Next.js now collects completely anonymous telemetry regarding usage.
This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry
▲ Next.js 16.2.1 (webpack)
- Experiments (use with caution):
· deferredEntries
· onBeforeDeferredEntries
⨯ serverMinification
Creating an optimized production build ...
Failed to compile.
./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node
Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
Import trace for requested module:
./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node
./node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js
./node_modules/.pnpm/@vercel+cli-auth@0.1.0/node_modules/@vercel/cli-auth/credentials-store.js
./node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/auth-config.js
./node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/token-util.js
./node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/index.js
./node_modules/.pnpm/@vercel+queue@0.1.4/node_modules/@vercel/queue/dist/index.mjs
./node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/queue.js
./node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/index.js
./node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime/world.js
./node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime.js
./node_modules/.pnpm/workflow@file+..+..+tarballs+workflow-5.0.0-beta.2.tgz_@nestjs+common@11.1.19_reflect-m_b69e931b2c51a2a5cba5d083f6730fe9/node_modules/workflow/dist/runtime.js
./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node
Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
Import trace for requested module:
./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node
./node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js
./node_modules/.pnpm/@vercel+cli-auth@0.1.0/node_modu
|
|
E2E Local Postgres Tests (nextjs-webpack - canary)
Process completed with exit code 1.
|
|
packages/core/e2e/local-build.test.ts > e2e > builds without errors:
packages/core/e2e/local-build.test.ts#L54
Error: Command "pnpm build" failed with exit code 1
> nextjs-webpack@0.0.2-alpha.5 prebuild /tmp/workflow-nextjs-webpack-0h7JuZ/workbench/nextjs-webpack
> pnpm generate:workflows
> nextjs-webpack@0.0.2-alpha.5 generate:workflows /tmp/workflow-nextjs-webpack-0h7JuZ/workbench/nextjs-webpack
> node ../scripts/generate-workflows-registry.js
✓ Generated ./_workflows.ts with 15 workflow(s)
- workflows/100_durable_agent_e2e.ts
- workflows/10_single_stmt_control_flow.ts
- workflows/1_simple.ts
- workflows/2_control_flow.ts
- workflows/3_streams.ts
- workflows/4_ai.ts
- workflows/5_hooks.ts
- workflows/6_batching.ts
- workflows/7_full.ts
- workflows/8_react_render.tsx
- workflows/98_duplicate_case.ts
- workflows/99_e2e.ts
- workflows/agent_chat.ts
- workflows/serde-models.ts
- workflows/serde-steps.ts
> nextjs-webpack@0.0.2-alpha.5 build /tmp/workflow-nextjs-webpack-0h7JuZ/workbench/nextjs-webpack
> next build --webpack
Attention: Next.js now collects completely anonymous telemetry regarding usage.
This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry
▲ Next.js 16.3.0-canary.2 (webpack)
- Experiments (use with caution):
· deferredEntries
· onBeforeDeferredEntries
⨯ serverMinification
Creating an optimized production build ...
Failed to compile.
./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node
Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
Import trace for requested module:
./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node
./node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js
./node_modules/.pnpm/@vercel+cli-auth@0.1.0/node_modules/@vercel/cli-auth/credentials-store.js
./node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/auth-config.js
./node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/token-util.js
./node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/index.js
./node_modules/.pnpm/@vercel+queue@0.1.4/node_modules/@vercel/queue/dist/index.mjs
./node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/queue.js
./node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/index.js
./node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime/world.js
./node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime.js
./node_modules/.pnpm/workflow@file+..+..+tarballs+workflow-5.0.0-beta.2.tgz_@nestjs+common@11.1.19_reflect-m_4c42f3f5f9f5fc457ff30c948191b6a5/node_modules/workflow/dist/runtime.js
./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node
Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)
Import trace for requested module:
./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node
./node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js
./node_modules/.pnpm/@vercel+cli-auth@0.1.0/
|
|
E2E Local Postgres Tests (nextjs-turbopack - stable)
Process completed with exit code 1.
|
|
packages/core/e2e/local-build.test.ts > e2e > builds without errors:
packages/core/e2e/local-build.test.ts#L54
Error: Command "pnpm build" failed with exit code 1
> nextjs-turbopack@0.0.2-alpha.5 prebuild /tmp/workflow-nextjs-turbopack-6zMix5/workbench/nextjs-turbopack
> pnpm generate:workflows
> nextjs-turbopack@0.0.2-alpha.5 generate:workflows /tmp/workflow-nextjs-turbopack-6zMix5/workbench/nextjs-turbopack
> node ../scripts/generate-workflows-registry.js
✓ Generated ./_workflows.ts with 19 workflow(s)
- workflows/100_durable_agent_e2e.ts
- workflows/10_single_stmt_control_flow.ts
- workflows/1_simple.ts
- workflows/2_control_flow.ts
- workflows/3_streams.ts
- workflows/4_ai.ts
- workflows/5_hooks.ts
- workflows/6_batching.ts
- workflows/7_full.ts
- workflows/8_react_render.tsx
- workflows/96_many_steps.ts
- workflows/97_bench.ts
- workflows/98_duplicate_case.ts
- workflows/99_e2e.ts
- workflows/agent_chat.ts
- workflows/serde-models.ts
- workflows/serde-steps.ts
- workflows/server_action_step_import_helpers.ts
- workflows/server_action_step_imports.ts
> nextjs-turbopack@0.0.2-alpha.5 build /tmp/workflow-nextjs-turbopack-6zMix5/workbench/nextjs-turbopack
> next build --turbopack
Attention: Next.js now collects completely anonymous telemetry regarding usage.
This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry
▲ Next.js 16.2.1 (Turbopack)
- Experiments (use with caution):
· deferredEntries
· onBeforeDeferredEntries
Creating an optimized production build ...
> Build error occurred
Error: Turbopack build failed with 2 errors:
./workbench/nextjs-turbopack/node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js
non-ecmascript placeable asset
asset is not placeable in ESM chunks, so it doesn't have a module id
Import traces:
App Route:
./workbench/nextjs-turbopack/node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+cli-auth@0.1.0/node_modules/@vercel/cli-auth/credentials-store.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/auth-config.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/token-util.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/index.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+queue@0.1.4/node_modules/@vercel/queue/dist/index.mjs
./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/queue.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/index.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime/world.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime/run.js
./workbench/nextjs-turbopack/app/api/chat/[runId]/stream/route.ts
Instrumentation:
./workbench/nextjs-turbopack/node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+cli-auth@0.1.0/node_modules/@vercel/cli-auth/credentials-store.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/auth-config.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/token-util.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/index
|
|
E2E Local Postgres Tests (nextjs-turbopack - canary)
Process completed with exit code 1.
|
|
packages/core/e2e/local-build.test.ts > e2e > builds without errors:
packages/core/e2e/local-build.test.ts#L54
Error: Command "pnpm build" failed with exit code 1
> nextjs-turbopack@0.0.2-alpha.5 prebuild /tmp/workflow-nextjs-turbopack-x2MB7d/workbench/nextjs-turbopack
> pnpm generate:workflows
> nextjs-turbopack@0.0.2-alpha.5 generate:workflows /tmp/workflow-nextjs-turbopack-x2MB7d/workbench/nextjs-turbopack
> node ../scripts/generate-workflows-registry.js
✓ Generated ./_workflows.ts with 19 workflow(s)
- workflows/100_durable_agent_e2e.ts
- workflows/10_single_stmt_control_flow.ts
- workflows/1_simple.ts
- workflows/2_control_flow.ts
- workflows/3_streams.ts
- workflows/4_ai.ts
- workflows/5_hooks.ts
- workflows/6_batching.ts
- workflows/7_full.ts
- workflows/8_react_render.tsx
- workflows/96_many_steps.ts
- workflows/97_bench.ts
- workflows/98_duplicate_case.ts
- workflows/99_e2e.ts
- workflows/agent_chat.ts
- workflows/serde-models.ts
- workflows/serde-steps.ts
- workflows/server_action_step_import_helpers.ts
- workflows/server_action_step_imports.ts
> nextjs-turbopack@0.0.2-alpha.5 build /tmp/workflow-nextjs-turbopack-x2MB7d/workbench/nextjs-turbopack
> next build --turbopack
Attention: Next.js now collects completely anonymous telemetry regarding usage.
This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry
▲ Next.js 16.3.0-canary.2 (Turbopack)
- Experiments (use with caution):
· deferredEntries
· onBeforeDeferredEntries
Creating an optimized production build ...
> Build error occurred
Error: Turbopack build failed with 2 errors:
./workbench/nextjs-turbopack/node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js
non-ecmascript placeable asset
asset is not placeable in ESM chunks, so it doesn't have a module id
Import traces:
App Route:
./workbench/nextjs-turbopack/node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+cli-auth@0.1.0/node_modules/@vercel/cli-auth/credentials-store.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/auth-config.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/token-util.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/index.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+queue@0.1.4/node_modules/@vercel/queue/dist/index.mjs
./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/queue.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/index.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime/world.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime/run.js
./workbench/nextjs-turbopack/app/api/chat/[runId]/stream/route.ts
Instrumentation:
./workbench/nextjs-turbopack/node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+cli-auth@0.1.0/node_modules/@vercel/cli-auth/credentials-store.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/auth-config.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/token-util.js
./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/d
|
|
E2E Local Postgres Tests (nest - stable)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Postgres Tests (nest - stable)
The operation was canceled.
|
|
E2E Local Dev Tests (hono - stable)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Dev Tests (hono - stable)
The operation was canceled.
|
|
E2E Local Dev Tests (express - stable)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Dev Tests (express - stable)
The operation was canceled.
|
|
E2E Vercel Prod Tests (express)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Vercel Prod Tests (express)
The operation was canceled.
|
|
E2E Vercel Prod Tests (nextjs-webpack)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Vercel Prod Tests (nextjs-webpack)
The operation was canceled.
|
|
E2E Local Postgres Tests (vite - stable)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Postgres Tests (vite - stable)
The operation was canceled.
|
|
E2E Vercel Prod Tests (astro)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Vercel Prod Tests (astro)
The operation was canceled.
|
|
E2E Local Postgres Tests (nuxt - stable)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Postgres Tests (nuxt - stable)
The operation was canceled.
|
|
E2E Local Postgres Tests (nitro - stable)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Postgres Tests (nitro - stable)
The operation was canceled.
|
|
E2E Local Dev Tests (fastify - stable)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Dev Tests (fastify - stable)
The operation was canceled.
|
|
E2E Vercel Prod Tests (hono)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Vercel Prod Tests (sveltekit)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Vercel Prod Tests (hono)
The operation was canceled.
|
|
E2E Local Dev Tests (nextjs-webpack - stable)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Vercel Prod Tests (sveltekit)
The operation was canceled.
|
|
E2E Local Dev Tests (nextjs-webpack - stable)
The operation was canceled.
|
|
E2E Local Dev Tests (vite - stable)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Dev Tests (vite - stable)
The operation was canceled.
|
|
E2E Local Dev Tests (nextjs-turbopack - stable)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Dev Tests (nextjs-turbopack - stable)
The operation was canceled.
|
|
E2E Local Prod Tests (hono - stable)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Prod Tests (hono - stable)
The operation was canceled.
|
|
E2E Local Dev Tests (nextjs-turbopack - canary)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Dev Tests (nextjs-turbopack - canary)
The operation was canceled.
|
|
E2E Local Dev Tests (nextjs-webpack - canary)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Dev Tests (nextjs-webpack - canary)
The operation was canceled.
|
|
E2E Local Prod Tests (astro - stable)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Prod Tests (astro - stable)
The operation was canceled.
|
|
E2E Local Prod Tests (express - stable)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Prod Tests (express - stable)
The operation was canceled.
|
|
E2E Local Dev Tests (nest - stable)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Dev Tests (nest - stable)
The operation was canceled.
|
|
E2E Local Postgres Tests (astro - stable)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Postgres Tests (astro - stable)
The operation was canceled.
|
|
E2E Local Postgres Tests (hono - stable)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Postgres Tests (hono - stable)
The operation was canceled.
|
|
E2E Local Postgres Tests (fastify - stable)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Postgres Tests (fastify - stable)
The operation was canceled.
|
|
E2E Windows Tests
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Windows Tests
The operation was canceled.
|
|
E2E Vercel Prod Tests (example)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Vercel Prod Tests (example)
The operation was canceled.
|
|
E2E Vercel Prod Tests (vite)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Vercel Prod Tests (vite)
The operation was canceled.
|
|
E2E Vercel Prod Tests (nuxt)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Vercel Prod Tests (nuxt)
The operation was canceled.
|
|
E2E Vercel Prod Tests (fastify)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Vercel Prod Tests (fastify)
The operation was canceled.
|
|
E2E Vercel Prod Tests (nextjs-turbopack)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Vercel Prod Tests (nextjs-turbopack)
The operation was canceled.
|
|
E2E Vercel Prod Tests (nitro)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Vercel Prod Tests (nitro)
The operation was canceled.
|
|
E2E Local Dev Tests (nitro - stable)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Dev Tests (nitro - stable)
The operation was canceled.
|
|
E2E Local Prod Tests (nitro - stable)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Prod Tests (nitro - stable)
The operation was canceled.
|
|
E2E Local Dev Tests (nuxt - stable)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Dev Tests (nuxt - stable)
The operation was canceled.
|
|
E2E Local Prod Tests (nest - stable)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Prod Tests (nest - stable)
The operation was canceled.
|
|
E2E Local Prod Tests (nuxt - stable)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Prod Tests (nuxt - stable)
The operation was canceled.
|
|
E2E Local Dev Tests (astro - stable)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Dev Tests (astro - stable)
The operation was canceled.
|
|
E2E Local Prod Tests (sveltekit - stable)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Prod Tests (sveltekit - stable)
The operation was canceled.
|
|
E2E Local Prod Tests (fastify - stable)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Prod Tests (fastify - stable)
The operation was canceled.
|
|
E2E Local Postgres Tests (express - stable)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Postgres Tests (express - stable)
The operation was canceled.
|
|
E2E Local Prod Tests (vite - stable)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Prod Tests (vite - stable)
The operation was canceled.
|
|
E2E Local Dev Tests (sveltekit - stable)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Dev Tests (sveltekit - stable)
The operation was canceled.
|
|
E2E Local Postgres Tests (sveltekit - stable)
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
E2E Local Postgres Tests (sveltekit - stable)
The operation was canceled.
|
|
E2E Required Check
Process completed with exit code 1.
|
|
Tests
Canceling since a higher priority waiting request for Tests-refs/pull/1858/merge exists
|
|
Create PR Comment
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, marocchino/sticky-pull-request-comment@v2, peter-evans/find-comment@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/
|
|
Get Test Matrix
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. 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/
|
|
Unit Tests (ubuntu-latest)
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. 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/
|
|
Vitest Plugin Tests
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. 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/
|
|
E2E Local Prod Tests (nextjs-webpack - stable)
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/upload-artifact@v4. 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/
|
|
Node.js Module Build Errors 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. 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/
|
|
E2E Local Prod Tests (nextjs-webpack - canary)
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/upload-artifact@v4. 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/
|
|
E2E Local Prod Tests (nextjs-turbopack - canary)
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/upload-artifact@v4. 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/
|
|
E2E Local Prod Tests (nextjs-turbopack - stable)
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/upload-artifact@v4. 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/
|
|
Unit Tests (windows-latest)
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. 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/
|
|
E2E Local Postgres Tests (nextjs-webpack - stable)
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/upload-artifact@v4. 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/
|
|
E2E Local Postgres Tests (nextjs-webpack - canary)
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/upload-artifact@v4. 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/
|
|
E2E Local Postgres Tests (nextjs-turbopack - stable)
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/upload-artifact@v4. 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/
|
|
E2E Local Postgres Tests (nextjs-turbopack - canary)
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/upload-artifact@v4. 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/
|
|
E2E Local Postgres Tests (nest - stable)
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/upload-artifact@v4. 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/
|
|
E2E Local Dev Tests (hono - stable)
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/upload-artifact@v4. 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/
|
|
E2E Local Dev Tests (express - stable)
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/upload-artifact@v4. 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/
|
|
E2E Vercel Prod Tests (express)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/actions/wait-for-vercel-project, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. 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/
|
|
E2E Vercel Prod Tests (nextjs-webpack)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/actions/wait-for-vercel-project, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. 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/
|
|
E2E Local Postgres Tests (vite - stable)
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/upload-artifact@v4. 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/
|
|
E2E Vercel Prod Tests (astro)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/actions/wait-for-vercel-project, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. 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/
|
|
E2E Local Postgres Tests (nuxt - stable)
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/upload-artifact@v4. 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/
|
|
E2E Local Postgres Tests (nitro - stable)
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/upload-artifact@v4. 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/
|
|
E2E Local Dev Tests (fastify - stable)
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/upload-artifact@v4. 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/
|
|
E2E Vercel Prod Tests (hono)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/actions/wait-for-vercel-project, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. 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/
|
|
E2E Local Dev Tests (nextjs-webpack - stable)
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/upload-artifact@v4. 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/
|
|
E2E Vercel Prod Tests (sveltekit)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/actions/wait-for-vercel-project, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. 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/
|
|
E2E Local Dev Tests (vite - stable)
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/upload-artifact@v4. 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/
|
|
E2E Local Dev Tests (nextjs-turbopack - stable)
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/upload-artifact@v4. 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/
|
|
E2E Local Prod Tests (hono - stable)
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/upload-artifact@v4. 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/
|
|
E2E Local Dev Tests (nextjs-turbopack - canary)
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/upload-artifact@v4. 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/
|
|
E2E Local Dev Tests (nextjs-webpack - canary)
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/upload-artifact@v4. 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/
|
|
E2E Local Prod Tests (astro - stable)
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/upload-artifact@v4. 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/
|
|
E2E Local Prod Tests (express - stable)
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/upload-artifact@v4. 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/
|
|
E2E Local Dev Tests (nest - stable)
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/upload-artifact@v4. 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/
|
|
E2E Local Postgres Tests (astro - stable)
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/upload-artifact@v4. 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/
|
|
E2E Local Postgres Tests (hono - stable)
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/upload-artifact@v4. 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/
|
|
E2E Local Postgres Tests (fastify - stable)
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/upload-artifact@v4. 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/
|
|
E2E Windows Tests
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/upload-artifact@v4. 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/
|
|
E2E Vercel Prod Tests (example)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/actions/wait-for-vercel-project, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. 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/
|
|
E2E Vercel Prod Tests (vite)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/actions/wait-for-vercel-project, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. 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/
|
|
E2E Vercel Prod Tests (nuxt)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/actions/wait-for-vercel-project, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. 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/
|
|
E2E Vercel Prod Tests (fastify)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/actions/wait-for-vercel-project, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. 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/
|
|
E2E Vercel Prod Tests (nextjs-turbopack)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/actions/wait-for-vercel-project, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. 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/
|
|
E2E Vercel Prod Tests (nitro)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/actions/wait-for-vercel-project, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. 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/
|
|
E2E Local Dev Tests (nitro - stable)
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/upload-artifact@v4. 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/
|
|
E2E Local Prod Tests (nitro - stable)
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/upload-artifact@v4. 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/
|
|
E2E Local Dev Tests (nuxt - stable)
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/upload-artifact@v4. 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/
|
|
E2E Local Prod Tests (nest - stable)
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/upload-artifact@v4. 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/
|
|
E2E Local Prod Tests (nuxt - stable)
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/upload-artifact@v4. 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/
|
|
E2E Local Dev Tests (astro - stable)
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/upload-artifact@v4. 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/
|
|
E2E Local Prod Tests (sveltekit - stable)
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/upload-artifact@v4. 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/
|
|
E2E Local Prod Tests (fastify - stable)
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/upload-artifact@v4. 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/
|
|
E2E Local Postgres Tests (express - stable)
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/upload-artifact@v4. 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/
|
|
E2E Local Prod Tests (vite - stable)
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/upload-artifact@v4. 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/
|
|
E2E Local Dev Tests (sveltekit - stable)
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/upload-artifact@v4. 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/
|
|
E2E Local Postgres Tests (sveltekit - stable)
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/upload-artifact@v4. 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 | |
|---|---|---|---|
|
nextjs-server-logs-windows
Expired
|
2.29 KB |
sha256:662b0e288cd6c0edf85b52802e59dc2ac829be7f35f9a7bdd69722ed6dd6453f
|
|