Use bun for autoupgrade when CLI installed via bun add -g

[alfonso-noriega]

WHY are these changes introduced?

When the global Shopify CLI is installed via bun add -g @shopify/cli, the autoupgrade flow incorrectly shells out to npm install -g @shopify/cli@latest instead of using bun. Reproduction:

$ SHOPIFY_CLI_FORCE_AUTO_UPGRADE=1 shopify version
0.0.0-snapshot-20260513102036
Upgrading Shopify CLI by running: `npm install -g @shopify/cli@latest`...
npm is no longer supported in a global context.
Please migrate to pnpm, or come talk to us in #dev-up.
💡 Version 3.94.3 available! Run `npm install -g @shopify/cli@latest`
$ which shopify
/Users/fonso/.bun/bin/shopify

Root cause: inferPackageManagerForGlobalCLI in packages/cli-kit/src/public/node/is-global.ts only looked at the resolved realpathSync(argv[1]) to decide which package manager to use. But bun add -g creates ~/.bun/bin/<name> as a symlink whose target is ../../node_modules/<pkg>/bin/run.js, which resolves to <HOME>/node_modules/<pkg>/bin/run.js — a path that no longer contains the string bun. Detection fell through to the default npm branch, so the autoupgrade and the upgrade-available reminder both suggested the wrong command.

WHAT is this pull request doing?

• Inspects both the unresolved symlink path (argv[1], e.g. ~/.bun/bin/shopify) and the resolved real path when matching the yarn / pnpm / bun signal. The original symlink under the package manager's bin dir is the most reliable indicator when the real path leaves that directory.
• Keeps the existing Homebrew detection (env var first, then /cellar/ in the resolved path) unchanged.
• Adds a regression test that mirrors the exact reproduction: a symlink at ~/.bun/bin/shopify resolving to <HOME>/node_modules/@shopify/cli/bin/run.js.

How to test your changes?

1. Install bun (e.g. via Homebrew: brew install bun).
2. bun add -g @shopify/cli and confirm which shopify returns a path under ~/.bun/bin.
3. With this branch's cli-kit build, run SHOPIFY_CLI_FORCE_AUTO_UPGRADE=1 shopify version.
4. Expected: the upgrade message reads Upgrading Shopify CLI by running: `bun install -g @shopify/cli@latest`... and bun (not npm) performs the install.

Unit tests:

pnpm --filter @shopify/cli-kit vitest run src/public/node/is-global.test.ts

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows) — fix is symmetric across platforms; the only path-shape assumption is that bun's bin dir contains the substring bun, which holds on all OSes.
• I've considered possible documentation changes — none needed; behavior matches what users already expect.
• I've considered analytics changes to measure impact — none needed.
• The change is user-facing — bug fix, but no changeset is included in this PR per request. If shipped on its own it should be a patch.

[alfonso-noriega]

• Use bun for autoupgrade when CLI installed via bun add -g #7556 👈 (View in Graphite)
• Fix Windows auto-upgrade for local CLI installs #7555
• main

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

[alfonso-noriega]

/snapit

[github-actions]

🫰✨ Thanks @alfonso-noriega! Your snapshot has been published to npm.

Test the snapshot by installing your package globally:

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

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.