Shopify has released CLI 4.0, a significant update to its command-line development tool that introduces semantic versioning, automatic updates, and removes several deprecated flags and commands. For Shopify developers and the agencies that support them, this release marks a meaningful shift in how Shopify approaches developer tooling - one that will affect daily workflows and deployment processes.
What has changed in Shopify CLI 4.0
The headline changes in CLI 4.0 centre on three areas:
Semantic Versioning (SemVer) Adoption
Shopify CLI now follows semantic versioning conventions. This means that version numbers will clearly communicate the nature of changes: major versions for breaking changes, minor versions for new features, and patch versions for bug fixes. For development teams, this brings predictability to upgrade planning. You'll know at a glance whether a new CLI release requires changes to your workflows or can be adopted safely.
Automatic Updates
CLI 4.0 introduces automatic updates, keeping your tooling current without manual intervention. This is a double-edged sword worth understanding. On the positive side, it ensures developers always have the latest security patches and feature access. On the cautious side, teams with CI/CD pipelines that depend on specific CLI behaviour will want to test their pipelines against auto-updated versions and consider pinning versions in production environments where stability is paramount.
Removal of Deprecated Commands and Flags
The --force flag has been removed, along with several deprecated commands. If your team's scripts or documentation reference these, they'll need updating. This is the kind of cleanup that's easy to overlook but can cause CI/CD failures if not addressed proactively.
Why this matters for merchants and agencies
CLI updates might seem like pure developer territory, but the implications ripple through the entire merchant experience.
Faster, more reliable development cycles
Semantic versioning gives development teams and their agency partners clearer signals about what any given upgrade involves. A patch update (4.0.0 to 4.0.1) is low-risk maintenance. A minor update (4.0 to 4.1) brings new features without breaking changes. A major update (4.x to 5.0) planned signals work is required. This clarity translates directly to more predictable project timelines and fewer surprise issues during deployments.
The Shopify Scripts deprecation deadline is now five weeks away
This CLI update arrives at a critical moment. Shopify Scripts will stop executing entirely on June 30, 2026. As of 15 April, editing and publishing Scripts was already disabled. If your store relies on Scripts for custom pricing, discount logic, or shipping rules, migration to Shopify Functions or a public app is now urgent. There is no grace period and no further extension expected.
CLI 4.0 is the tool you will use to build and deploy Functions. The removal of deprecated commands in CLI 4.0 is part of Shopify's broader commitment to moving the ecosystem forward - and merchants need their development teams to keep pace.
Other important updates were released alongside CLI 4.0
Next Generation Events in developer preview
Shopify announced Next Generation Events in developer preview. These improve on traditional webhooks with field-level trigger control, custom GraphQL payloads, and filters. For merchants, this means apps can be more precise about what data they react to, reducing unnecessary API calls and improving overall performance.
Expiring offline access tokens - required by January 2027
A critical security change was also announced alongside CLI 4.0: starting 1 January 2027, all public apps must use expiring offline access tokens for Admin API calls. Apps still using non-expiring tokens after that date will receive authentication errors. This extends the April 2026 change, which applied only to newly created public apps, to all public apps. If you are running public apps on your store, confirm with your app providers that they are preparing for this transition now.
Other notable May changelog updates
Several additional merchant-facing improvements are worth noting. Shopify Messaging now supports automated SMS for abandoned cart and checkout recovery. Merchants operating multiple brands or entities in the same country can now use separate Shopify Payments accounts managed from a single store. Time-series metrics in Shopify Analytics now offer a cumulative toggle for running totals. And a new two-column layout with brand customisation options has been added to the customer account sign-in page.
What you should do now
For development teams:
-
Test your CI/CD pipelines with CLI 4.0 immediately.
-
Audit any scripts or documentation that reference removed flags or commands.
-
Decide on your auto-update strategy - embrace it for development environments, consider pinning for production pipelines.
-
Begin migrating any remaining Shopify Scripts to Functions before the June 30 deadline.
For merchants:
-
Ask your development team or agency partner about their CLI 4.0 readiness.
-
Confirm your Scripts migration plan is on track - this is the final month.
-
Evaluate the new SMS automation capabilities in Shopify Messaging against your current third-party SMS tools.
-
If you operate multiple brands, investigate the new multi-entity Shopify Payments support.
The bigger picture
Shopify CLI 4.0 is more than a tooling update. Semantic versioning, auto-updates, and the removal of legacy features all signal a platform that is tightening its standards and expecting its ecosystem to operate at a higher level of professionalism. For merchants and agencies in the Shopify ecosystem, the message is clear: the platform is moving fast, and staying current with tooling is not optional. It is the foundation for everything else.
How On Tap can help
At On Tap, we are an eCommerce agency helping merchants and development teams navigate platform updates and build future-ready Shopify stores. Whether you need support with your Scripts migration before the 30 June deadline or want to discuss your broader Shopify strategy, get in touch with our team.
