Friendlier auto-upgrade messaging (version range + success banner)#7547
Merged
Conversation
Before:
Upgrading Shopify CLI by running: `pnpm add -g @shopify/cli@latest`...
After:
✨ New version of Shopify CLI available! (3.94.3 → 3.95.0)
Now upgrading by running: `pnpm add -g @shopify/cli@latest`...
[package manager output]
╭─ success ──────────────────────────────╮
│ Shopify CLI upgraded │
│ │
│ You're now on version 3.95.0. │
╰────────────────────────────────────────╯
- Pre-message now states *what just happened* ("new version
available") and shows the version range when known.
- Adds a `renderSuccess` banner after a successful upgrade so users
get explicit confirmation instead of silence.
- The version range comes from `checkForCachedNewVersion`, which
is already populated by `versionToAutoUpgrade()` upstream — no
extra network call.
Contributor
|
/snapit |
Contributor
|
🫰✨ Thanks @nickwesselman! 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-20260514141436Caution After installing, validate the version by running |
Contributor
nickwesselman
approved these changes
May 14, 2026
isaacroldan
approved these changes
May 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

WHY are these changes introduced?
Today the auto-upgrade flow prints a single, easy-to-miss line and then nothing else (until the next prompt) when it's done:
There's no acknowledgement of why it's running, no version context, and no confirmation when it finished — a side-effect ran on the user's machine and we leave them guessing.
WHAT is this pull request doing?
Two minimal, additive changes in
packages/cli-kit/src/public/node/upgrade.ts(runCLIUpgradeonly, and only on the global path — local-project upgrades are unchanged):1. Friendlier pre-message with the version range.
The version range is derived from
checkForCachedNewVersion, which is already populated byversionToAutoUpgrade()upstream — it's a synchronous cache read, no extra network call, no signature change.2. Green
renderSuccessbanner after a successful upgrade.Reuses
renderSuccessfrom@shopify/cli-kit/node/ui— the same banner used elsewhere in the CLI for deploy confirmations, so no new visual primitives.Diff
packages/cli-kit/src/public/node/upgrade.ts— +17 / -1.How to test your changes?
cd packages/cli-kit pnpm vitest run src/public/node/upgrade.test.ts pnpm type-checkEnd-to-end (snapshot-based, same as the bug bash setup):
You should see the new pre-message with the version range, the package-manager output, then the green success banner.
Checklist
env_auto_upgrade_successmetadata is unchanged