Shopify CLI Deadline for Password-Protected Stores: Upgrade Before October 2026

Shopify has announced a firm deadline for theme developers: starting October 1, 2026, Shopify CLI versions 3.83.x and earlier will no longer support theme-development workflows against password-protected storefronts. Version 3.84.0 is the minimum supported release for that scenario.

If your team develops themes on protected client shops, preview stores, or stores that are not ready for public traffic, check every workstation and CI environment now. A working setup can fail after the deadline even when the theme code itself has not changed.

Who is affected

The change is narrowly scoped but common in professional theme work. You are affected when both conditions are true:

1. The target storefront is password protected.
2. The theme command is running through Shopify CLI 3.83.x or older.

Shopify calls out these likely workflows:

• shopify theme dev
• shopify theme console
• shopify app dev when the app contains theme app extensions

The reason is authentication rather than Liquid compatibility. Older CLI versions use a legacy storefront-authentication implementation that Shopify will stop supporting for protected-store development sessions.

Check your installed version

Run:

shopify version

Do not rely on the version recorded in an old setup document. Check the executable that your shell actually resolves on each machine, then check CI images and developer containers separately.

At the time of Shopify's August 27 announcement, the minimum acceptable version was 3.84.0 and Shopify recommended the then-current 4.7.0 release. Install the latest available version rather than pinning to the minimum unless your organization has a tested compatibility constraint.

For npm installations, Shopify's upgrade command is:

npm install -g @shopify/cli@latest

Then close and reopen the terminal if necessary and verify again:

shopify version

If the old number still appears, your system may have multiple CLI installations on the path. Find which executable is active before uninstalling anything, especially on shared or managed computers.

Upgrade without disrupting the team

A global package update is quick, but a reliable migration includes the surrounding workflow:

1. Record the current CLI and Node.js versions.
2. Upgrade one development environment first.
3. Authenticate against a non-critical protected store.
4. Run shopify theme dev and open its preview URL.
5. Confirm hot reload, asset updates, section rendering, and editor deep links.
6. Test shopify theme console if the team uses it.
7. Test shopify app dev for projects with theme app extensions.
8. Update onboarding docs, CI images, and version managers.
9. Roll the verified setup out to the remaining developers before October 1.

The fallback Shopify mentions is removing storefront password protection. That can expose a store that was intentionally private, so it should not be the default response. Upgrading the CLI preserves the intended access boundary and is usually the safer operational choice.

Watch for version drift

Teams often upgrade the laptop used for testing but miss another execution environment:

• a second developer's workstation;
• a remote development container;
• a CI runner built from a cached image;
• a freelancer's documented setup command;
• an app repository that invokes theme extension development;
• a machine with both npm and another package-manager installation.

Add shopify version to troubleshooting templates and environment audit scripts. You do not need to commit generated theme output just to prove the upgrade; preserve your normal source-control workflow and compare only intentional changes.

What this does not require

This announcement does not require you to rewrite sections, update Liquid syntax, change JSON templates, or remove storefront password protection. It changes which CLI versions can authenticate theme-development flows for protected stores.

It is also separate from Shopify's July 2026 Liquid developer preview. If you are evaluating the new tags described in the block and partial preview guide, update the CLI and preview features as two independent tasks.

A short team checklist

• Every developer reports Shopify CLI 3.84.0 or later.
• The team standard uses the latest tested release.
• Protected-store theme dev preview works.
• Theme console works where required.
• Theme app extension development works.
• CI and container images use the updated package.
• Onboarding documentation no longer installs an old version.
• A rollback note records the previously working environment without exposing credentials.

Shopify's deprecation announcement is the source of truth for the date, affected versions, and commands. Because the recommended latest CLI version changes over time, always confirm it in Shopify's current documentation rather than copying 4.7.0 into a permanent version policy.

Once the environment is current, use the HTML to Liquid converter for component conversion and the manual review checklist before moving generated Liquid into a client theme.