Skip to content

Run function GraphQL typegen with the project package manager #3988

Run function GraphQL typegen with the project package manager

Run function GraphQL typegen with the project package manager #3988

Triggered via pull request April 13, 2026 16:16
Status Failure
Total duration 5m 40s
Artifacts

tests-pr.yml

on: pull_request
Matrix: unit-tests
Type check
1m 5s
Type check
Lint
1m 38s
Lint
Bundle
50s
Bundle
Knip (unused code check)
33s
Knip (unused code check)
Check graphql-codegen has been run
5m 35s
Check graphql-codegen has been run
Check OCLIF manifests & readme & docs
52s
Check OCLIF manifests & readme & docs
E2E tests
48s
E2E tests
Type-diff
48s
Type-diff
Unit tests
4s
Unit tests
Fit to window
Zoom out
Zoom in

Annotations

38 errors and 22 warnings
Type-diff
Process completed with exit code 130.
Type-diff
Module '"@shopify/cli-kit/node/node-package-manager"' has no exported member 'packageManagerBinaryCommandForDirectory'.
E2E tests
Process completed with exit code 130.
E2E tests
Module '"@shopify/cli-kit/node/node-package-manager"' has no exported member 'packageManagerBinaryCommandForDirectory'.
Bundle
Process completed with exit code 130.
Bundle
Module '"@shopify/cli-kit/node/node-package-manager"' has no exported member 'packageManagerBinaryCommandForDirectory'.
Check OCLIF manifests & readme & docs
Process completed with exit code 130.
Check OCLIF manifests & readme & docs
Module '"@shopify/cli-kit/node/node-package-manager"' has no exported member 'packageManagerBinaryCommandForDirectory'.
Type check
Process completed with exit code 130.
Type check
Module '"@shopify/cli-kit/node/node-package-manager"' has no exported member 'packageManagerBinaryCommandForDirectory'.
Type check
Module '"@shopify/cli-kit/node/node-package-manager"' has no exported member 'packageManagerBinaryCommandForDirectory'.
Type check
Module '"@shopify/cli-kit/node/node-package-manager"' has no exported member 'packageManagerBinaryCommandForDirectory'.
Unit tests with Node 22.2.0 in ubuntu-latest
Process completed with exit code 1.
src/cli/services/generate/extension.test.ts > initialize a extension > does not rename graphql files in src: packages/app/src/cli/services/function/build.ts#L147
Error: [vitest] No "packageManagerBinaryCommandForDirectory" export is defined on the "@shopify/cli-kit/node/node-package-manager" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: vi.mock(import("@shopify/cli-kit/node/node-package-manager"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ buildGraphqlTypes src/cli/services/function/build.ts:147:25 ❯ Object.task src/cli/services/generate/extension.ts:212:15 ❯ runTask ../cli-kit/src/private/node/ui/components/Tasks.tsx:47:25 ❯ runTasks ../cli-kit/src/private/node/ui/components/Tasks.tsx:79:30
Unit tests with Node 24.1.0 in windows-latest (shard 2/2)
The strategy configuration was canceled because "unit-tests.ubuntu-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.ubuntu-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 22.2.0 in windows-latest (shard 2/2)
The strategy configuration was canceled because "unit-tests.ubuntu-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 22.2.0 in windows-latest (shard 1/2)
The strategy configuration was canceled because "unit-tests.ubuntu-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 24.1.0 in ubuntu-latest
The strategy configuration was canceled because "unit-tests.ubuntu-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 macos-latest
The strategy configuration was canceled because "unit-tests.ubuntu-latest_22_2_0" failed
Unit tests with Node 24.1.0 in macos-latest
The operation was canceled.
Unit tests with Node 20.14.0 in macos-latest
The strategy configuration was canceled because "unit-tests.ubuntu-latest_22_2_0" failed
Unit tests with Node 20.14.0 in macos-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.ubuntu-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 20.14.0 in windows-latest (shard 2/2)
The strategy configuration was canceled because "unit-tests.ubuntu-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 20.14.0 in ubuntu-latest
The strategy configuration was canceled because "unit-tests.ubuntu-latest_22_2_0" failed
Unit tests with Node 20.14.0 in ubuntu-latest
The operation was canceled.
Unit tests with Node 22.2.0 in macos-latest
The strategy configuration was canceled because "unit-tests.ubuntu-latest_22_2_0" failed
Unit tests with Node 22.2.0 in macos-latest
The operation was canceled.
Unit tests
Process completed with exit code 1.
Check graphql-codegen has been run
Process completed with exit code 1.
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/
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/
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, 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/
E2E tests
No files were found with the provided path: packages/e2e/test-results/. No artifacts will be uploaded.
E2E tests
No files were found with the provided path: packages/e2e/playwright-report/. No artifacts will be uploaded.
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/
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/
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/
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 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 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 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 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 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 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 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 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 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/
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/