Skip to content

Add breaking change detection CI check #4530

Add breaking change detection CI check

Add breaking change detection CI check #4530

Triggered via pull request April 21, 2026 13:01
Status Cancelled
Total duration 6m 39s
Artifacts

tests-pr.yml

on: pull_request
Matrix: unit-tests
Breaking change detection
1m 33s
Breaking change detection
Type check
1m 12s
Type check
Lint
1m 27s
Lint
Bundle
1m 1s
Bundle
Knip (unused code check)
28s
Knip (unused code check)
Check graphql-codegen has been run
5m 57s
Check graphql-codegen has been run
Check OCLIF manifests & readme & docs
1m 45s
Check OCLIF manifests & readme & docs
E2E tests
6m 6s
E2E tests
Type-diff
1m 36s
Type-diff
Unit tests
2s
Unit tests
Breaking change approval
2s
Breaking change approval
Fit to window
Zoom out
Zoom in

Annotations

57 errors and 21 warnings
Breaking change detection
Process completed with exit code 1.
Breaking change detection
Breaking changes detected. A member of @shopify/dev_experience must approve the breaking-change-approval environment.
src/cli/services/app/config-pipeline-snapshot.test.ts > Config pipeline snapshots > subscriptions with same URI but different include_fields stay separate through round-trip: packages/app/src/cli/services/app/config-pipeline-snapshot.test.ts#L12
Error: Required ❯ parseConfigAsCurrentApp src/cli/services/app/config-pipeline-snapshot.test.ts:12:28 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:294:23 ❯ inTemporaryDirectory ../cli-kit/src/public/node/fs.ts:81:12 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:274:5
src/cli/services/app/config-pipeline-snapshot.test.ts > Config pipeline snapshots > subscriptions with same URI but different filters stay separate through round-trip: packages/app/src/cli/services/app/config-pipeline-snapshot.test.ts#L12
Error: Required ❯ parseConfigAsCurrentApp src/cli/services/app/config-pipeline-snapshot.test.ts:12:28 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:258:23 ❯ inTemporaryDirectory ../cli-kit/src/public/node/fs.ts:81:12 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:238:5
src/cli/services/app/config-pipeline-snapshot.test.ts > Config pipeline snapshots > config with relative webhook URIs stabilizes after round-trip: packages/app/src/cli/services/app/config-pipeline-snapshot.test.ts#L12
Error: Required ❯ parseConfigAsCurrentApp src/cli/services/app/config-pipeline-snapshot.test.ts:12:28 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:198:23 ❯ inTemporaryDirectory ../cli-kit/src/public/node/fs.ts:81:12 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:179:5
src/cli/services/app/config-pipeline-snapshot.test.ts > Config pipeline snapshots > webhook subscriptions with mixed topics and compliance topics produce stable output: packages/app/src/cli/services/app/config-pipeline-snapshot.test.ts#L12
Error: Required ❯ parseConfigAsCurrentApp src/cli/services/app/config-pipeline-snapshot.test.ts:12:28 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:168:28 ❯ inTemporaryDirectory ../cli-kit/src/public/node/fs.ts:81:12 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:132:5
src/cli/services/app/config-pipeline-snapshot.test.ts > Config pipeline snapshots > config round-trip stabilizes after second write: packages/app/src/cli/services/app/config-pipeline-snapshot.test.ts#L12
Error: Required ❯ parseConfigAsCurrentApp src/cli/services/app/config-pipeline-snapshot.test.ts:12:28 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:118:23 ❯ inTemporaryDirectory ../cli-kit/src/public/node/fs.ts:81:12 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:112:5
src/cli/services/app/config-pipeline-snapshot.test.ts > Config pipeline snapshots > config round-trip (write → read → write) reorders webhook subscriptions: packages/app/src/cli/services/app/config-pipeline-snapshot.test.ts#L12
Error: Required ❯ parseConfigAsCurrentApp src/cli/services/app/config-pipeline-snapshot.test.ts:12:28 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:97:28 ❯ inTemporaryDirectory ../cli-kit/src/public/node/fs.ts:81:12 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:89:5
src/cli/models/extensions/extension-instance.test.ts > bundleConfig > returns the uuid from extensionsNonUuidManaged when the extension is not uuid managed: packages/app/src/cli/models/extensions/extension-instance.test.ts#L306
AssertionError: expected undefined to deeply equal ObjectContaining {"uuid": "uuid"} - Expected: ObjectContaining { "uuid": "uuid", } + Received: undefined ❯ src/cli/models/extensions/extension-instance.test.ts:306:17
src/cli/models/extensions/extension-instance.test.ts > deployConfig > returns transformed config when defined: packages/app/src/cli/models/extensions/extension-instance.test.ts#L229
AssertionError: expected undefined to match object { embedded: true } - Expected: { "embedded": true, } + Received: undefined ❯ src/cli/models/extensions/extension-instance.test.ts:229:17
src/cli/models/app/loader.test.ts > load > loads the app with a Pos configuration app access extension configured inside the toml file: packages/app/src/cli/models/app/loader.ts#L310
Error: Validation errors in /var/folders/tb/y368xp_x10s3ty1b_mtl5mxr0000gn/T/tmp-BijjmzmFaN0y/shopify.app.toml: [pos.is_embedded]: Required ❯ loadAppFromContext src/cli/models/app/loader.ts:310:11 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { tryMessage: null, nextSteps: undefined, customSections: undefined, skipOclifErrorHandling: true }
src/cli/services/deploy.test.ts > deploy > pushes the configuration extension if include config on deploy : packages/app/src/cli/services/deploy.test.ts#L434
AssertionError: expected "uploadExtensionsBundle" to be called with arguments: [ { appManifest: { …(3) }, …(9) } ] Received: 1st uploadExtensionsBundle call: @@ -5,30 +5,22 @@ "appManifest": { "handle": "", "modules": [ { "assets": "point_of_sale", - "config": Any<Object>, + "config": {}, "handle": "point_of_sale", "target": "", "type": "point_of_sale_external", "uid": "point_of_sale", "uuid": undefined, }, ], "name": "App", }, - "appModules": [ - { - "config": "{\"embedded\":true}", - "context": "", - "handle": "point_of_sale", - "specificationIdentifier": undefined, - "uid": "point_of_sale", - "uuid": "point_of_sale", - }, - ], + "appModules": [], + "bundlePath": undefined, "commitReference": "https://github.com/deploytest/repo/commit/d4e5ce7999242b200acde378654d62c14b211bcc", "developerPlatformClient": { "accountInfo": [Function spy], "activeAppVersion": [Function spy], "apiSchemaDefinition": [Function spy], @@ -83,10 +75,12 @@ "updateExtension": [Function spy], "updateURLs": [Function spy], "webUiName": "Test Dashboard", }, "extensionIds": {}, + "message": undefined, "name": "App", "organizationId": "org-id", "release": true, + "version": undefined, }, ] Number of calls: 1 ❯ src/cli/services/deploy.test.ts:434:36
Unit tests with Node 20.14.0 in macos-latest
The strategy configuration was canceled because "unit-tests.macos-latest_22_2_0" failed
src/cli/services/app/config-pipeline-snapshot.test.ts > Config pipeline snapshots > subscriptions with same URI but different include_fields stay separate through round-trip: packages/app/src/cli/services/app/config-pipeline-snapshot.test.ts#L12
Error: Required ❯ parseConfigAsCurrentApp src/cli/services/app/config-pipeline-snapshot.test.ts:12:28 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:294:23 ❯ inTemporaryDirectory ../cli-kit/src/public/node/fs.ts:81:12 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:274:5
src/cli/services/app/config-pipeline-snapshot.test.ts > Config pipeline snapshots > subscriptions with same URI but different filters stay separate through round-trip: packages/app/src/cli/services/app/config-pipeline-snapshot.test.ts#L12
Error: Required ❯ parseConfigAsCurrentApp src/cli/services/app/config-pipeline-snapshot.test.ts:12:28 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:258:23 ❯ inTemporaryDirectory ../cli-kit/src/public/node/fs.ts:81:12 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:238:5
src/cli/services/app/config-pipeline-snapshot.test.ts > Config pipeline snapshots > config with relative webhook URIs stabilizes after round-trip: packages/app/src/cli/services/app/config-pipeline-snapshot.test.ts#L12
Error: Required ❯ parseConfigAsCurrentApp src/cli/services/app/config-pipeline-snapshot.test.ts:12:28 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:198:23 ❯ inTemporaryDirectory ../cli-kit/src/public/node/fs.ts:81:12 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:179:5
src/cli/services/app/config-pipeline-snapshot.test.ts > Config pipeline snapshots > webhook subscriptions with mixed topics and compliance topics produce stable output: packages/app/src/cli/services/app/config-pipeline-snapshot.test.ts#L12
Error: Required ❯ parseConfigAsCurrentApp src/cli/services/app/config-pipeline-snapshot.test.ts:12:28 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:168:28 ❯ inTemporaryDirectory ../cli-kit/src/public/node/fs.ts:81:12 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:132:5
src/cli/services/app/config-pipeline-snapshot.test.ts > Config pipeline snapshots > config round-trip stabilizes after second write: packages/app/src/cli/services/app/config-pipeline-snapshot.test.ts#L12
Error: Required ❯ parseConfigAsCurrentApp src/cli/services/app/config-pipeline-snapshot.test.ts:12:28 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:118:23 ❯ inTemporaryDirectory ../cli-kit/src/public/node/fs.ts:81:12 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:112:5
src/cli/services/app/config-pipeline-snapshot.test.ts > Config pipeline snapshots > config round-trip (write → read → write) reorders webhook subscriptions: packages/app/src/cli/services/app/config-pipeline-snapshot.test.ts#L12
Error: Required ❯ parseConfigAsCurrentApp src/cli/services/app/config-pipeline-snapshot.test.ts:12:28 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:97:28 ❯ inTemporaryDirectory ../cli-kit/src/public/node/fs.ts:81:12 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:89:5
src/cli/models/app/loader.test.ts > load > loads the app with a Pos configuration app access extension configured inside the toml file: packages/app/src/cli/models/app/loader.ts#L310
Error: Validation errors in /var/folders/tb/y368xp_x10s3ty1b_mtl5mxr0000gn/T/tmp-d7psMiB1LMdo/shopify.app.toml: [pos.is_embedded]: Required ❯ loadAppFromContext src/cli/models/app/loader.ts:310:11 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { tryMessage: null, nextSteps: undefined, customSections: undefined, skipOclifErrorHandling: true }
src/cli/models/extensions/extension-instance.test.ts > bundleConfig > returns the uuid from extensionsNonUuidManaged when the extension is not uuid managed: packages/app/src/cli/models/extensions/extension-instance.test.ts#L306
AssertionError: expected undefined to deeply equal ObjectContaining {"uuid": "uuid"} - Expected: ObjectContaining { "uuid": "uuid", } + Received: undefined ❯ src/cli/models/extensions/extension-instance.test.ts:306:17
src/cli/models/extensions/extension-instance.test.ts > deployConfig > returns transformed config when defined: packages/app/src/cli/models/extensions/extension-instance.test.ts#L229
AssertionError: expected undefined to match object { embedded: true } - Expected: { "embedded": true, } + Received: undefined ❯ src/cli/models/extensions/extension-instance.test.ts:229:17
src/cli/services/deploy.test.ts > deploy > pushes the configuration extension if include config on deploy : packages/app/src/cli/services/deploy.test.ts#L434
AssertionError: expected "uploadExtensionsBundle" to be called with arguments: [ { appManifest: { …(3) }, …(9) } ] Received: 1st uploadExtensionsBundle call: @@ -5,30 +5,22 @@ "appManifest": { "handle": "", "modules": [ { "assets": "point_of_sale", - "config": Any<Object>, + "config": {}, "handle": "point_of_sale", "target": "", "type": "point_of_sale_external", "uid": "point_of_sale", "uuid": undefined, }, ], "name": "App", }, - "appModules": [ - { - "config": "{\"embedded\":true}", - "context": "", - "handle": "point_of_sale", - "specificationIdentifier": undefined, - "uid": "point_of_sale", - "uuid": "point_of_sale", - }, - ], + "appModules": [], + "bundlePath": undefined, "commitReference": "https://github.com/deploytest/repo/commit/d4e5ce7999242b200acde378654d62c14b211bcc", "developerPlatformClient": { "accountInfo": [Function spy], "activeAppVersion": [Function spy], "apiSchemaDefinition": [Function spy], @@ -83,10 +75,12 @@ "updateExtension": [Function spy], "updateURLs": [Function spy], "webUiName": "Test Dashboard", }, "extensionIds": {}, + "message": undefined, "name": "App", "organizationId": "org-id", "release": true, + "version": undefined, }, ] Number of calls: 1 ❯ src/cli/services/deploy.test.ts:434:36
Unit tests with Node 20.14.0 in windows-latest (shard 2/2)
The strategy configuration was canceled because "unit-tests.macos-latest_22_2_0" failed
Unit tests with Node 20.14.0 in windows-latest (shard 2/2)
The operation was canceled.
Unit tests with Node 22.2.0 in ubuntu-latest
The strategy configuration was canceled because "unit-tests.macos-latest_22_2_0" failed
src/cli/services/app/config-pipeline-snapshot.test.ts > Config pipeline snapshots > subscriptions with same URI but different include_fields stay separate through round-trip: packages/app/src/cli/services/app/config-pipeline-snapshot.test.ts#L12
Error: Required ❯ parseConfigAsCurrentApp src/cli/services/app/config-pipeline-snapshot.test.ts:12:28 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:294:23 ❯ inTemporaryDirectory ../cli-kit/src/public/node/fs.ts:81:12 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:274:5
src/cli/services/app/config-pipeline-snapshot.test.ts > Config pipeline snapshots > subscriptions with same URI but different filters stay separate through round-trip: packages/app/src/cli/services/app/config-pipeline-snapshot.test.ts#L12
Error: Required ❯ parseConfigAsCurrentApp src/cli/services/app/config-pipeline-snapshot.test.ts:12:28 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:258:23 ❯ inTemporaryDirectory ../cli-kit/src/public/node/fs.ts:81:12 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:238:5
src/cli/services/app/config-pipeline-snapshot.test.ts > Config pipeline snapshots > config with relative webhook URIs stabilizes after round-trip: packages/app/src/cli/services/app/config-pipeline-snapshot.test.ts#L12
Error: Required ❯ parseConfigAsCurrentApp src/cli/services/app/config-pipeline-snapshot.test.ts:12:28 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:198:23 ❯ inTemporaryDirectory ../cli-kit/src/public/node/fs.ts:81:12 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:179:5
src/cli/services/app/config-pipeline-snapshot.test.ts > Config pipeline snapshots > webhook subscriptions with mixed topics and compliance topics produce stable output: packages/app/src/cli/services/app/config-pipeline-snapshot.test.ts#L12
Error: Required ❯ parseConfigAsCurrentApp src/cli/services/app/config-pipeline-snapshot.test.ts:12:28 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:168:28 ❯ inTemporaryDirectory ../cli-kit/src/public/node/fs.ts:81:12 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:132:5
src/cli/services/app/config-pipeline-snapshot.test.ts > Config pipeline snapshots > config round-trip stabilizes after second write: packages/app/src/cli/services/app/config-pipeline-snapshot.test.ts#L12
Error: Required ❯ parseConfigAsCurrentApp src/cli/services/app/config-pipeline-snapshot.test.ts:12:28 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:118:23 ❯ inTemporaryDirectory ../cli-kit/src/public/node/fs.ts:81:12 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:112:5
src/cli/services/app/config-pipeline-snapshot.test.ts > Config pipeline snapshots > config round-trip (write → read → write) reorders webhook subscriptions: packages/app/src/cli/services/app/config-pipeline-snapshot.test.ts#L12
Error: Required ❯ parseConfigAsCurrentApp src/cli/services/app/config-pipeline-snapshot.test.ts:12:28 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:97:28 ❯ inTemporaryDirectory ../cli-kit/src/public/node/fs.ts:81:12 ❯ src/cli/services/app/config-pipeline-snapshot.test.ts:89:5
src/cli/models/extensions/extension-instance.test.ts > bundleConfig > returns the uuid from extensionsNonUuidManaged when the extension is not uuid managed: packages/app/src/cli/models/extensions/extension-instance.test.ts#L306
AssertionError: expected undefined to deeply equal ObjectContaining {"uuid": "uuid"} - Expected: ObjectContaining { "uuid": "uuid", } + Received: undefined ❯ src/cli/models/extensions/extension-instance.test.ts:306:17
src/cli/models/extensions/extension-instance.test.ts > deployConfig > returns transformed config when defined: packages/app/src/cli/models/extensions/extension-instance.test.ts#L229
AssertionError: expected undefined to match object { embedded: true } - Expected: { "embedded": true, } + Received: undefined ❯ src/cli/models/extensions/extension-instance.test.ts:229:17
src/cli/models/app/loader.test.ts > load > loads the app with a Pos configuration app access extension configured inside the toml file: packages/app/src/cli/models/app/loader.ts#L310
Error: Validation errors in /tmp/tmp-XXXXXXaULdsT/shopify.app.toml: [pos.is_embedded]: Required ❯ loadAppFromContext src/cli/models/app/loader.ts:310:11 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { tryMessage: null, nextSteps: undefined, customSections: undefined, skipOclifErrorHandling: true }
src/cli/services/deploy.test.ts > deploy > pushes the configuration extension if include config on deploy : packages/app/src/cli/services/deploy.test.ts#L434
AssertionError: expected "uploadExtensionsBundle" to be called with arguments: [ { appManifest: { …(3) }, …(9) } ] Received: 1st uploadExtensionsBundle call: @@ -5,30 +5,22 @@ "appManifest": { "handle": "", "modules": [ { "assets": "point_of_sale", - "config": Any<Object>, + "config": {}, "handle": "point_of_sale", "target": "", "type": "point_of_sale_external", "uid": "point_of_sale", "uuid": undefined, }, ], "name": "App", }, - "appModules": [ - { - "config": "{\"embedded\":true}", - "context": "", - "handle": "point_of_sale", - "specificationIdentifier": undefined, - "uid": "point_of_sale", - "uuid": "point_of_sale", - }, - ], + "appModules": [], + "bundlePath": undefined, "commitReference": "https://github.com/deploytest/repo/commit/d4e5ce7999242b200acde378654d62c14b211bcc", "developerPlatformClient": { "accountInfo": [Function spy], "activeAppVersion": [Function spy], "apiSchemaDefinition": [Function spy], @@ -83,10 +75,12 @@ "updateExtension": [Function spy], "updateURLs": [Function spy], "webUiName": "Test Dashboard", }, "extensionIds": {}, + "message": undefined, "name": "App", "organizationId": "org-id", "release": true, + "version": undefined, }, ] Number of calls: 1 ❯ src/cli/services/deploy.test.ts:434:36
Unit tests with Node 22.2.0 in windows-latest (shard 2/2)
The strategy configuration was canceled because "unit-tests.macos-latest_22_2_0" failed
Unit tests with Node 22.2.0 in windows-latest (shard 2/2)
The operation was canceled.
Unit tests with Node 24.1.0 in windows-latest (shard 2/2)
The strategy configuration was canceled because "unit-tests.macos-latest_22_2_0" failed
Unit tests with Node 24.1.0 in windows-latest (shard 2/2)
The operation was canceled.
Unit tests with Node 20.14.0 in windows-latest (shard 1/2)
The strategy configuration was canceled because "unit-tests.macos-latest_22_2_0" failed
Unit tests with Node 20.14.0 in windows-latest (shard 1/2)
The operation was canceled.
Unit tests with Node 24.1.0 in ubuntu-latest
The strategy configuration was canceled because "unit-tests.macos-latest_22_2_0" failed
Unit tests with Node 24.1.0 in ubuntu-latest
The operation was canceled.
Unit tests with Node 24.1.0 in windows-latest (shard 1/2)
The strategy configuration was canceled because "unit-tests.macos-latest_22_2_0" failed
Unit tests with Node 24.1.0 in windows-latest (shard 1/2)
The operation was canceled.
Unit tests with Node 22.2.0 in windows-latest (shard 1/2)
The strategy configuration was canceled because "unit-tests.macos-latest_22_2_0" failed
Unit tests with Node 22.2.0 in windows-latest (shard 1/2)
The operation was canceled.
Unit tests with Node 20.14.0 in ubuntu-latest
The strategy configuration was canceled because "unit-tests.macos-latest_22_2_0" failed
Unit tests with Node 20.14.0 in ubuntu-latest
The operation was canceled.
Unit tests with Node 24.1.0 in macos-latest
The strategy configuration was canceled because "unit-tests.macos-latest_22_2_0" failed
Unit tests with Node 24.1.0 in macos-latest
The operation was canceled.
Unit tests
Process completed with exit code 1.
Check graphql-codegen has been run
Canceling since a higher priority waiting request for shopify-cli-major-change-check exists
E2E tests
Canceling since a higher priority waiting request for shopify-cli-major-change-check exists
E2E tests
The operation was canceled.
PR
Canceling since a higher priority waiting request for shopify-cli-major-change-check exists
Knip (unused code check)
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/
Bundle
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/
Type check
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/
Lint
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/
Breaking change detection
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, marocchino/sticky-pull-request-comment@fcf6fe9e4a0409cd9316a5011435be0f3327f1e1, 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/
Type-diff
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/
Check OCLIF manifests & readme & docs
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/
Unit tests with Node 22.2.0 in macos-latest
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/
Unit tests with Node 20.14.0 in macos-latest
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/
Unit tests with Node 20.14.0 in windows-latest (shard 2/2)
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/
Unit tests with Node 22.2.0 in 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@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/
Unit tests with Node 22.2.0 in windows-latest (shard 2/2)
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/
Unit tests with Node 24.1.0 in windows-latest (shard 2/2)
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/
Unit tests with Node 20.14.0 in windows-latest (shard 1/2)
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/
Unit tests with Node 24.1.0 in 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@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/
Unit tests with Node 24.1.0 in windows-latest (shard 1/2)
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/
Unit tests with Node 22.2.0 in windows-latest (shard 1/2)
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/
Unit tests with Node 20.14.0 in 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@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/
Unit tests with Node 24.1.0 in macos-latest
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/
Check graphql-codegen has been run
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/
E2E tests
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/