fix: add packageManager back (pnpm v10 auto-adds it during install) #19

EPERM, Permission denied: \\?\C:\Users\RUNNER~1\AppData\Local\Temp\qwik-router-1775190172522-oopt6h45qkn '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\qwik-router-1775190172522-oopt6h45qkn'

Router - command stubs return 0 / add command stub executes and returns 0: tests/unit/router.spec.ts#L100

Test timeout

Test on node / windows-latest /

Process completed with exit code 1.

Router - command stubs return 0 / add command stub executes and returns 0: tests/unit/router.spec.ts#L89

EPERM, Permission denied: \\?\C:\Users\RUNNER~1\AppData\Local\Temp\qwik-router-1775190243007-zbxttjqutt '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\qwik-router-1775190243007-zbxttjqutt'

Router - command stubs return 0 / add command stub executes and returns 0: tests/unit/router.spec.ts#L100

Test timeout

Test on deno / windows-latest /

Process completed with exit code 1.

CRE-03 -- create-qwik playground / scaffolds playground starter with counter component: tests/integration/golden/create-qwik.spec.ts#L98

expected 1 to equal +0 - Expected - 1 + Received + 1 - 0 + 1

CRE-02 -- create-qwik library / scaffolds library starter with valid package.json: tests/integration/golden/create-qwik.spec.ts#L64

expected 1 to equal +0 - Expected - 1 + Received + 1 - 0 + 1

CRE-01 -- create-qwik empty / scaffolds empty starter with package.json containing @qwik.dev/core: tests/integration/golden/create-qwik.spec.ts#L26

expected 1 to equal +0 - Expected - 1 + Received + 1 - 0 + 1

Router - command stubs return 0 / add command stub executes and returns 0: tests/unit/router.spec.ts#L31

not found: pnpm

Router - COMMANDS dynamic imports / migrate-v2 command resolves to a module with a default constructor: tests/unit/router.spec.ts#L31

not found: pnpm

Router - COMMANDS dynamic imports / add command resolves to a module with a default constructor: tests/unit/router.spec.ts#L31

not found: pnpm

Quality checks

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

Test on bun / 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 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/

Test on bun / ubuntu-latest /

No lock file found in project directory: /home/runner/work/cli/cli. Skipping cache restore.

Test on bun / ubuntu-latest / pnpm

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, pnpm/action-setup@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/

Test on deno / ubuntu-latest /

No lock file found in project directory: /home/runner/work/cli/cli. Skipping cache restore.

Test on deno / ubuntu-latest / pnpm

Test on bun / macos-latest /

No lock file found in project directory: /Users/runner/work/cli/cli. Skipping cache restore.

Test on bun / ubuntu-latest / yarn

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/

Test on node / ubuntu-latest /