Default to pnpm/pnpx internally

[gonzaloriestra]

WHY are these changes introduced?

We should align internal tooling with the repo’s default package manager (pnpm), so contributors and CI use the same commands.

WHAT is this pull request doing?

• Root create-app script: Passes --package-manager pnpm into the create-app dev entrypoint.
• E2E: Default packageManager in packages/e2e/setup/app.ts is pnpm when E2E_PACKAGE_MANAGER is unset; Playwright steps in tests-pr.yml use pnpm exec playwright so CI uses the workspace’s pinned Playwright (avoids pnpx pulling a different version). E2E helper script comments / create-app flows updated for pnpm where relevant.
• Misc: Small script and workflow/doc tweaks (e.g. dev.yml, build-dev-docs.sh, create-notification-pr.js, release.yml) for consistency with pnpm-first usage.

How to test your changes?

CI

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes
• I've considered analytics changes to measure impact
• The change is user-facing, so I've added a changelog entry with pnpm changeset add

[gonzaloriestra]

• Default to pnpm/pnpx internally #7254 👈 (View in Graphite)
• Fix getPackageManager logic with workspaces #7253
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[gonzaloriestra]

/snapit

[gonzaloriestra]

/snapit

[github-actions]

Differences in type declarations

We detected differences in the type declarations generated by Typescript for this branch compared to the baseline ('main' branch). Please, review them to ensure they are backward-compatible. Here are some important things to keep in mind:

• Some seemingly private modules might be re-exported through public modules.
• If the branch is behind main you might see odd diffs, rebase main into this branch.

New type declarations

We found no new type declarations in this PR

Existing type declarations

packages/cli-kit/dist/public/node/node-package-manager.d.ts

@@ -60,6 +60,10 @@ export declare class FindUpAndReadPackageJsonNotFoundError extends BugError {
 export declare function packageManagerFromUserAgent(env?: NodeJS.ProcessEnv): PackageManager;
 /**
  * Returns the dependency manager used in a directory.
+ * Walks upward from  so workspace packages (e.g. )
+ * still resolve to the repo root lockfile ().
+ * If no lockfile is found, it falls back to the package manager from the user agent.
+ * If the package manager from the user agent is unknown, it returns 'npm'.
  * @param fromDirectory - The starting directory
  * @returns The dependency manager
  */

[github-actions]

🫰✨ Thanks @gonzaloriestra! Your snapshot has been published to npm.

Test the snapshot by installing your package globally:

npm i -g --@shopify:registry=https://registry.npmjs.org @shopify/cli@0.0.0-snapshot-20260413113709

Caution

After installing, validate the version by running shopify version in your terminal.
If the versions don't match, you might have multiple global instances installed.
Use which shopify to find out which one you are running and uninstall it.