Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- The deadline is October 1, 2026. Affected workflows are Theme development against password-protected storefronts using CLI 3.83.x or earlier.
- Shopify identifies shopify theme dev, shopify theme console and shopify app dev with theme app extensions as high-risk commands.
- The official minimum is 3.84.0. Shopify recommends the current latest release and checking the executable actually in use with shopify version.
- Stores without password protection are outside this deprecation. Removing the storefront password is an officially listed alternative, but must not be done on production stores without business approval.
- An upgrade is not complete migration. Validate preview, console and theme-extension workflows separately by store, authentication method and command.
The scenario: unchanged local code, but a password-protected store no longer previews
An agency runs shopify theme dev across client stores. Public stores work, while password-protected development or staging stores fail to establish preview/session access. Common misdiagnoses blame theme code, store permissions, proxy IPs or temporary login failures, leading to repeated sign-ins, network changes or theme rebuilding.
Do not start by deleting the store password. Run shopify version in the terminal actually executing the command and record store, CLI version, authentication method and failed command. If it is 3.83.x or earlier and the target storefront is password-protected, address this deprecation first.
What happened: legacy storefront authentication retires on October 1
Shopify’s developer announcement explicitly requires Shopify CLI 3.84.0 or later for Theme commands on password-protected storefronts from October 1, 2026. Legacy storefront authentication used by 3.83.x and earlier will no longer be supported.
This does not retire every Shopify CLI command or every store simultaneously. Scope is theme development for password-protected stores; unprotected storefronts are outside the announcement. Do not confuse this deadline with ScriptTag migration, which has different audiences, authentication paths and remediation.
Map impact by store, version, command and authentication
For every environment, record storefront password status, shopify version output, command entry point and owner. Prioritize shopify theme dev, shopify theme console and shopify app dev when the project includes theme app extensions. Inventory local development, shared previews, CI and emergency-maintenance environments separately.
Also record the authentication method: Shopify account, Theme Access password or custom-app access token. Official CLI documentation says that without --password, the CLI attempts Shopify-account credentials. An authentication failure after upgrading therefore cannot be attributed to this deprecation from symptoms alone; compare actual parameters and account permissions.
Upgrade, confirm the version and regress each command
For npm installations, follow the official announcement with npm install -g @shopify/cli@latest, then run shopify version. The minimum is 3.84.0; at publication, the announcement recommended latest version 4.7.0. For other package managers, follow their installation documentation rather than retaining several sources and verifying only one.
After version confirmation, choose a non-production or recoverable store and run the theme dev, theme console and theme-extension app dev commands actually used. Confirm development-theme creation, live-preview access, console connection to the correct store and theme-extension loading. Then proceed in store batches, retaining version, command, store and verification time.
Failures, stop conditions and rollback
If shopify version still shows an old release, inspect the current shell PATH, package-manager source and CI image instead of assuming repeated reinstallations changed it. If the new version fails only for some stores, preserve the original error and check store target, Themes permissions, Theme Access password, custom-app scopes and command arguments.
Stop broad rollout and ask the store owner to decide if the upgrade interrupts several stores, the executable actually used cannot be established or the only alternative requires removing a production storefront password. Rollback must restore a validated toolchain only. Do not expose protected stores without authorization to bypass authentication deprecation.
Network boundary: do not misdiagnose a version cutoff as a proxy failure
This change concerns legacy CLI storefront preview/session authentication, not network-egress rules. Consult the proxy connection troubleshooting checklist only with accompanying DNS, TLS, 407 or timeout evidence, or clearly divergent results across networks.
Changing IPs, clearing browser cache or signing in repeatedly will not restore official support for 3.83.x after the deadline. Conversely, 3.84.0 or later will not automatically repair account permissions, an incorrect store, missing scopes or theme-directory structure. Validate the version requirement separately from runtime failures.
Recheck before the deadline and update this page for later facts
Inventory all environments and test upgrades now. By mid-September, eliminate password-protected-store workflows still using 3.83.x or earlier. In September’s final week, rerun the three command types with actual accounts. For failures after October 1, compare password-protection status and CLI version before investigating permissions or networking.
If Shopify changes the deadline, minimum version, affected commands or authentication boundary, update this page rather than creating similar theme dev, theme console or app dev pages. Record pass rates, failed stores, authentication methods and owners to distinguish platform rules, environment drift and store-specific permissions.
Sources
Frequently Asked Questions
When does older Shopify Theme CLI stop supporting password-protected stores?
From October 1, 2026, Theme commands for password-protected storefronts require CLI 3.84.0 or later. Versions 3.83.x and earlier are no longer supported.
Which commands are most likely affected?
Shopify names shopify theme dev, shopify theme console and shopify app dev when the project includes theme app extensions.
What is the minimum upgrade version?
3.84.0. Official guidance recommends the current latest release and checking the actual runtime version with shopify version.
Are all Shopify stores affected?
No. The announcement covers theme development for password-protected storefronts. Unprotected stores are outside this deprecation.
Can I remove the store password to keep using the old CLI?
It is an officially listed alternative, but should not be used for production or confidential staging stores without business approval. Prefer upgrading and validating the toolchain.
What if theme dev still fails after upgrading?
Confirm the active version in PATH, then check the target store, account Themes permissions, Theme Access or custom-app credentials and scopes. Investigate proxies only with explicit network errors.