Password Protected Shop Dev flows on Shopify Theme CLI v3.83.x and older to be deprecated

What Changed

Shopify has announced a deprecation timeline for older versions of the Shopify CLI when working with password protected storefronts. Starting October 1, 2026, Theme commands on Shopify CLI will require version 3.84.0 or later to develop or preview themes on storefronts that have password protection enabled. Versions 3.83.x and earlier will no longer support these theme development workflows once the deadline passes.

This deprecation specifically affects the theme dev, theme pull, theme push, and related Theme commands when used against a storefront that has the password protection setting active, typically used for stores that are not yet publicly launched or that restrict access during development.

Why This Matters

Many Shopify theme developers and agencies use password protection during the build phase of a new store, before it goes live to customers. If local CLI tooling is not kept current, developers relying on older CLI versions will lose the ability to run local theme development servers or sync theme files against these protected storefronts after the cutoff date.

For agencies managing multiple client projects, CLI version fragmentation across teams or CI/CD pipelines could result in broken workflows if some environments still reference the older CLI binary.

Practical Implications

Developers should audit their current Shopify CLI version by running shopify version and upgrade to 3.84.0 or later before October 1, 2026. Teams using Docker images, CI pipelines, or documentation that pins a specific CLI version should update those references as part of this transition.

As an alternative, store owners can remove password protection from the storefront to continue using an older CLI version, though this exposes the store publicly and may not be suitable for pre-launch projects.

Shopify recommends checking the CLI changelog regularly, as theme tooling updates are released frequently and older versions may lose compatibility with other platform features over time.

Read the full announcement →