See all services Shopify Plus Partner
Action Required Developer

Upgrade Shopify CLI Before Password Protected Dev Breaks

From October 1, 2026, theme commands against password protected storefronts need Shopify CLI 3.84.0 or later. The real exposure is pinned versions in CI images, not developer laptops.

Executive summary

What changed

Older CLI versions authenticate against password protected storefronts using a legacy mechanism. Shopify is retiring support for that mechanism in theme development flows on October 1, 2026. Publicly accessible storefronts are unaffected.

The remedy is an upgrade to 3.84.0 or later, with 4.7.0 the current release. The documented alternative is to remove password protection from the storefront you develop against, which is rarely acceptable for a pre-launch store.

Why it matters

On its own this is a version bump. The risk is where CLI versions get pinned. Developers upgrade their local tooling out of habit, so laptops tend to be fine. Build images, CI runners, and container definitions do not upgrade themselves, and a Dockerfile pinned to 3.79 for reproducibility three years ago will keep resolving to 3.79 until someone changes it. That is the pin that fails, and it fails everywhere at once because every branch shares the image. Teams running staged theme work across multiple regional storefronts should treat this as a fleet check rather than a per developer one, which is the same discipline we apply on Shopify development engagements generally.

The timing also matters. October 1 sits directly against peak season preparation for most merchants. A tooling failure discovered in early October competes for attention with the code freeze, which is the worst possible week to be debugging authentication in a build pipeline.

Role-specific impact

Use-case example

Real-world scenario

A retailer maintains six regional storefronts, all password protected ahead of a coordinated launch, and builds themes through a shared Docker image pinned to CLI 3.79 so that builds stay reproducible across the team.

If nobody audits that pin, the failure arrives on October 2. Six teams find that shopify theme dev no longer connects, and the holiday theme freeze is two weeks out. The fix is a one line change to the image, but it lands in the worst week of the calendar. The same change made during a September audit takes about an afternoon and blocks nobody.

Implementation checklist

  1. Run shopify version on every machine and build image used for theme work.
  2. Upgrade anything below 3.84.0 with npm install -g @shopify/cli@latest, currently 4.7.0.
  3. Search CI configuration, Dockerfiles, and lockfiles for pinned @shopify/cli versions.
  4. Re-run shopify theme dev and shopify theme console against a password protected store to confirm the upgrade works.
  5. Check theme app extension workflows, since shopify app dev is also affected.
  6. Record October 1, 2026 in the release calendar and complete verification before the peak season freeze.

FAQ

Q: Does this affect stores that are not password protected?

A: No. Theme development against a publicly accessible storefront is unaffected. Only the legacy authentication used for password protected stores is being retired.

Q: Can we stay on an older CLI version?

A: Only by removing password protection from the storefront you develop against. For a pre-launch store that is usually unacceptable, so upgrading is the practical path.

Resources

Shopify documentation: Shopify CLI for themes.

Need guidance? Talk to Makro.