Process completed with exit code 130.

Object literal may only specify known properties, and 'include_config_on_deploy' does not exist in type '{ automatically_update_urls_on_dev?: boolean | undefined; dev_store_url?: string | undefined; }'.

Property 'include_config_on_deploy' does not exist on type '{ automatically_update_urls_on_dev?: boolean | undefined; dev_store_url?: string | undefined; }'.

Property 'include_config_on_deploy' does not exist on type '{ automatically_update_urls_on_dev?: boolean | undefined; dev_store_url?: string | undefined; }'.

Process completed with exit code 130.

Object literal may only specify known properties, and 'include_config_on_deploy' does not exist in type '{ automatically_update_urls_on_dev?: boolean | undefined; dev_store_url?: string | undefined; }'.

Property 'include_config_on_deploy' does not exist on type '{ automatically_update_urls_on_dev?: boolean | undefined; dev_store_url?: string | undefined; }'.

Property 'include_config_on_deploy' does not exist on type '{ automatically_update_urls_on_dev?: boolean | undefined; dev_store_url?: string | undefined; }'.

Process completed with exit code 130.

Object literal may only specify known properties, and 'include_config_on_deploy' does not exist in type '{ automatically_update_urls_on_dev?: boolean | undefined; dev_store_url?: string | undefined; }'.

Property 'include_config_on_deploy' does not exist on type '{ automatically_update_urls_on_dev?: boolean | undefined; dev_store_url?: string | undefined; }'.

Property 'include_config_on_deploy' does not exist on type '{ automatically_update_urls_on_dev?: boolean | undefined; dev_store_url?: string | undefined; }'.

Process completed with exit code 130.

Object literal may only specify known properties, and 'include_config_on_deploy' does not exist in type '{ automatically_update_urls_on_dev?: boolean | undefined; dev_store_url?: string | undefined; }'.

Property 'include_config_on_deploy' does not exist on type '{ automatically_update_urls_on_dev?: boolean | undefined; dev_store_url?: string | undefined; }'.

Property 'include_config_on_deploy' does not exist on type '{ automatically_update_urls_on_dev?: boolean | undefined; dev_store_url?: string | undefined; }'.

Process completed with exit code 130.

Object literal may only specify known properties, and 'include_config_on_deploy' does not exist in type '{ automatically_update_urls_on_dev?: boolean | undefined; dev_store_url?: string | undefined; }'.

Property 'include_config_on_deploy' does not exist on type '{ automatically_update_urls_on_dev?: boolean | undefined; dev_store_url?: string | undefined; }'.

Property 'include_config_on_deploy' does not exist on type '{ automatically_update_urls_on_dev?: boolean | undefined; dev_store_url?: string | undefined; }'.

Argument of type '{ name: string; client_id: string; application_url: string; embedded: boolean; webhooks: { api_version: string; }; build: { include_config_on_deploy: boolean; }; }' is not assignable to parameter of type 'CurrentAppConfiguration'.

Object literal may only specify known properties, and 'include_config_on_deploy' does not exist in type '{ automatically_update_urls_on_dev?: boolean | undefined; dev_store_url?: string | undefined; }'.

Object literal may only specify known properties, and 'include_config_on_deploy' does not exist in type '{ automatically_update_urls_on_dev?: boolean | undefined; dev_store_url?: string | undefined; }'.

Property 'include_config_on_deploy' does not exist on type '{ automatically_update_urls_on_dev?: boolean | undefined; dev_store_url?: string | undefined; }'.

Conversion of type '{ name: string; client_id: string; webhooks: { api_version: string; subscriptions: { topics: string[]; uri: string; }[]; }; application_url: string; build: { automatically_update_urls_on_dev: true; dev_store_url: string; include_config_on_deploy: boolean; }; access_scopes: { ...; }; }' to type 'CurrentAppConfiguration' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.

Conversion of type '{ name: string; client_id: string; webhooks: { api_version: string; subscriptions: { topics: string[]; uri: string; }[]; }; application_url: string; build: { automatically_update_urls_on_dev: true; dev_store_url: string; include_config_on_deploy: boolean; }; access_scopes: { ...; }; }' to type 'CurrentAppConfiguration' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.

Conversion of type '{ name: string; client_id: string; webhooks: { api_version: string; }; application_url: string; build: { automatically_update_urls_on_dev: true; dev_store_url: string; include_config_on_deploy: boolean; }; access_scopes: { ...; }; }' to type 'CurrentAppConfiguration' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.

Property 'include_config_on_deploy' does not exist on type '{ automatically_update_urls_on_dev?: boolean | undefined; dev_store_url?: string | undefined; }'.

Object literal may only specify known properties, and 'include_config_on_deploy' does not exist in type '{ automatically_update_urls_on_dev?: boolean | undefined; dev_store_url?: string | undefined; }'.

Object literal may only specify known properties, and 'include_config_on_deploy' does not exist in type '{ automatically_update_urls_on_dev?: boolean | undefined; dev_store_url?: string | undefined; }'.

Process completed with exit code 1.

Error: Snapshot `Config pipeline snapshots > subscription with both topics and compliance_topics on same URI splits after round-trip 1` mismatched - Expected + Received @@ -5,12 +5,11 @@ application_url = "https://myapp.example.com" embedded = true [build] automatically_update_urls_on_dev = true - dev_store_url = "test-store.myshopify.com" - include_config_on_deploy = true + dev_store_url = "test-store.myshopify.com" [access.admin] direct_api_mode = "online" embedded_app_direct_api_access = true ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:333:27 ❯ inTemporaryDirectory ../cli-kit/src/public/node/fs.ts:81:12 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:307:5

Error: Snapshot `Config pipeline snapshots > webhook subscriptions with mixed topics and compliance topics produce stable output 2` mismatched - Expected + Received @@ -5,12 +5,11 @@ application_url = "https://myapp.example.com" embedded = true [build] automatically_update_urls_on_dev = true - dev_store_url = "test-store.myshopify.com" - include_config_on_deploy = true + dev_store_url = "test-store.myshopify.com" [access.admin] direct_api_mode = "online" embedded_app_direct_api_access = true ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:171:27 ❯ inTemporaryDirectory ../cli-kit/src/public/node/fs.ts:81:12 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:132:5

Error: Snapshot `Config pipeline snapshots > config round-trip (write → read → write) reorders webhook subscriptions 1` mismatched - Expected + Received @@ -5,12 +5,11 @@ application_url = "https://myapp.example.com" embedded = true [build] automatically_update_urls_on_dev = true - dev_store_url = "test-store.myshopify.com" - include_config_on_deploy = true + dev_store_url = "test-store.myshopify.com" [access.admin] direct_api_mode = "online" embedded_app_direct_api_access = true ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:105:27 ❯ inTemporaryDirectory ../cli-kit/src/public/node/fs.ts:81:12 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:89:5

The strategy configuration was canceled because "unit-tests.windows-latest_20_14_0_2_" failed

The operation was canceled.

The strategy configuration was canceled because "unit-tests.windows-latest_20_14_0_2_" failed

The operation was canceled.

The strategy configuration was canceled because "unit-tests.windows-latest_20_14_0_2_" failed

The operation was canceled.

The strategy configuration was canceled because "unit-tests.windows-latest_20_14_0_2_" failed

The operation was canceled.

The strategy configuration was canceled because "unit-tests.windows-latest_20_14_0_2_" failed

The operation was canceled.

The strategy configuration was canceled because "unit-tests.windows-latest_20_14_0_2_" failed

The operation was canceled.

The strategy configuration was canceled because "unit-tests.windows-latest_20_14_0_2_" failed

The operation was canceled.

The strategy configuration was canceled because "unit-tests.windows-latest_20_14_0_2_" failed

The operation was canceled.

The strategy configuration was canceled because "unit-tests.windows-latest_20_14_0_2_" failed

The operation was canceled.

The strategy configuration was canceled because "unit-tests.windows-latest_20_14_0_2_" failed

The operation was canceled.

The strategy configuration was canceled because "unit-tests.windows-latest_20_14_0_2_" failed

The operation was canceled.

Process completed with exit code 1.

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

No files were found with the provided path: packages/e2e/test-results/. No artifacts will be uploaded.

No files were found with the provided path: packages/e2e/playwright-report/. No artifacts will be uploaded.

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