October 24, 2026 · Ahmed · More by Ahmed
Shopify CLI Dropped --force — Here's What Replaced It
Shopify CLI 4.0 removed --force from app deploy. Here's exactly what --allow-updates and --allow-deletes now require from an unattended pipeline.
Until May 2026, shopify app deploy and shopify app release had a single --force flag that skipped every confirmation prompt — including the prompt before permanently deleting extensions and their configuration on installed shops. --force made no distinction between a low-risk operation (adding or updating an extension) and a high-risk one (deleting it, which also deletes that extension's data on every shop where the app is installed). For a CI/CD pipeline running unattended, that was an all-or-nothing bet.
The Flag Split: --allow-updates and --allow-deletes
As of Shopify CLI 3.89, released January 23, 2026, two flags replaced the single switch: --allow-updates lets a deploy add new app configuration and extensions and update existing ones; --allow-deletes lets it delete them. Shopify's own description of --force was that it was "equivalent to using these flags together." Shopify's stated recommendation is to use --allow-updates alone as the default CI/CD flag, and to reserve --allow-deletes for manual, deliberate runs — because deleting app configuration or extensions also deletes related data on any store that has the app installed.
The Removal Timeline
--force was deprecated on March 25, 2026, with Shopify stating removal would land in a May 2026 release. It was removed on schedule in Shopify CLI 4.0, released May 21, 2026, which also dropped several other deprecated commands and flags in the same release: shopify webhook trigger (replaced by shopify app webhook trigger), shopify theme serve (replaced by shopify theme dev), shopify app generate schema (replaced by shopify app function schema), shopify app webhook trigger --shared-secret (replaced by --client-secret), and shopify app generate extension --type (replaced by --template). CLI 4.0 also introduced semantic versioning and automatic self-upgrades — though auto-upgrade is skipped in CI, for project-local installs, and for major versions.
What Changed for Pipeline Authentication
A separate but related change landed May 6, 2026: app deployment in CI/CD became available to all apps through app automation tokens issued from the Dev Dashboard, rather than the CLI tokens previously generated on the Partner Dashboard. The new tokens are scoped to a single app instead of an entire partner account. Existing Partner-Dashboard CLI tokens keep working until they expire, but Shopify recommends transitioning.
What a Pipeline Needs to Check Now
A script still calling --force after a CLI upgrade past 4.0 will fail outright, since the flag no longer exists. The fix is mechanical: replace it with --allow-updates for the default unattended path, and treat --allow-deletes as an explicit, reviewed step rather than something a nightly job runs automatically. Teams that haven't touched their deploy scripts since early 2026 are the ones most likely to be caught by this — the flag was announced, deprecated, and removed inside about five months.