Updated 26 Sep 2026: Shopify's live developer changelog now gives September 23, 2026—not October 1—as the cutoff for legacy protected-store Theme CLI authentication. Update the dossier to correct the deadline and reflect that the cutoff has now passed.

Key details

  1. Shopify announced the Theme CLI authentication deprecation on August 27, 2026.
  2. The live Shopify developer changelog now gives September 23, 2026 as the cutoff.
  3. BTN's original dossier captured an October 1 deadline; that date is now superseded by the live first-party page.
  4. Shopify CLI versions 3.83.x and earlier are affected for password-protected storefront development flows.
  5. Shopify CLI 3.84.0 or later remains the documented compatibility floor.
  6. Affected workflows can include `shopify theme dev`, `shopify theme console`, and `shopify app dev` when theme app extensions are involved.
  7. The change retires a legacy storefront preview/session-authentication implementation.
  8. Removing storefront password protection can keep old CLI versions working, but changes the shop's access policy.

What builders should take away

  1. Treat the migration as already effective: search developer machines, devcontainers, CI images and bootstrap scripts for Shopify CLI 3.83.x or older now.
  2. Upgrade to at least 3.84.0 and test `theme dev`, `theme console` and theme-app-extension workflows against an actual password-protected store.
  3. Add a minimum Shopify CLI version check to project setup or CI if protected-store theme development is business-critical.
  4. Do not rely on the superseded October 1 date from earlier copies or summaries of Shopify's announcement.
  5. Do not remove storefront password protection merely to avoid a tooling upgrade unless the exposure is explicitly acceptable.

What changed

Shopify's live August 27 developer changelog now states that Theme commands on Shopify CLI versions 3.83.x and earlier stopped being supported for password-protected storefronts on September 23, 2026. BTN's original dossier captured an October 1 deadline from the same announcement, so the canonical deadline has materially changed and has already passed. The affected releases rely on a legacy storefront preview/session-authentication path. Shopify still documents CLI 3.84.0 or later as the compatibility floor and recommends the latest release. Removing storefront password protection remains an alternative, but changes the store's access boundary rather than fixing the development toolchain.

Why it matters

This is no longer a future migration reminder. Any agency, theme developer or app team still running CLI 3.83.x or older against a protected store is now beyond Shopify's documented support boundary. Because the store itself can remain healthy, the failure may look like a local authentication or configuration problem. Teams should verify developer machines, CI images and project tooling now rather than planning around the superseded October 1 date.

The documented cutoff is now September 23

Shopify's current developer changelog says protected-store Theme commands require Shopify CLI 3.84.0 or later starting September 23, 2026. That is earlier than the October 1 date BTN captured when this dossier was first published. The live first-party page is the stronger current source and the dossier should follow it.

The break is scoped to password-protected storefront development

The cutoff affects Theme CLI commands using versions 3.83.x and earlier when the target storefront is password protected. Public storefronts do not depend on the same legacy preview/session-authentication path, so this is not a universal Shopify CLI shutdown.

Several ordinary theme workflows can fail together

Shopify identifies `shopify theme dev` and `shopify theme console` as likely affected workflows. `shopify app dev` can also be affected when an application includes theme app extensions and needs protected-store preview access.

Version 3.84.0 remains the compatibility floor

Shopify still documents 3.84.0 or later as the supported line and recommends upgrading to the latest CLI. CI images, devcontainers and setup scripts can therefore be checked mechanically rather than waiting for an authentication failure.

Removing the password is still a workaround, not an equivalent migration

Shopify notes that developers can remove storefront password protection and continue using an older CLI. That changes who can access the storefront and may be inappropriate for development, staging or pre-launch stores. Upgrading preserves the intended access control while moving off the retired authentication path.

What to watch next

  • Whether Shopify edits the effective date or compatibility floor again.
  • Any post-cutoff reports of old CLI versions failing differently across local, CI or app-extension workflows.
  • Compatibility fixes in current Shopify CLI releases for protected-store preview sessions.
  • Further retirement of legacy developer-authentication paths.

Still unclear

  • Shopify's live changelog does not explain why the documented deadline moved from the earlier October 1 date to September 23.
  • The cutoff is narrowly scoped to protected-store development, so teams that never use password-protected storefronts may see no impact.
  • Third-party wrappers around Shopify CLI may bundle or invoke their own CLI version and need separate verification.

Sources

Direct reading behind this dossier.

2 sources
Manage theme access
Shopify Developer primary_documentation

Current documentation for Theme Access credentials and protected theme-development access.

Discussion

Discussion is reader-contributed. Comments are not part of the BTN dossier or its editorial evidence.

0 visible comments

Join the discussion

Keep comments useful and relevant. Reader contributions may be moderated and are not BTN editorial evidence.

Sign in to comment