RepoJournal
Shopify Shopify
74 wires and counting

$ follow Shopify

Keep up with Shopify in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-09-03
stories 10
RSS Archive Topics

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

Shopify CLI starts asking for demo data on dev store creation

By RepoJournal · Filed · About Shopify

nickwesselman Ariel Caplan
2 people shipped this
nickwesselman @nickwesselman 3 cited Ariel Caplan @amcaplan 1 cited

Shopify CLI's interactive dev store creation now prompts for demo data, and the `--with-demo-data` flag becomes tri-state `--demo-data`.

Shopify CLI improves the interactive dev store creation flow. `shopify store create dev` now asks whether to populate the new store with demo data after the name and plan prompts, so developers creating stores interactively, including through the inline flow in `app dev`, get the same option that `--with-demo-data` provided non-interactively [1]. The flag itself is renamed from `--with-demo-data` to `--demo-data` with `allowNo`, giving it standard tri-state behavior: `--demo-data` and `--no-demo-data` answer the question outright, while unspecified flags prompt in interactive terminals and default to false in non-interactive contexts. This is a breaking change for any scripts using the old flag name [2].

The same flow gets explanatory context when an organization has no dev stores. `app dev` now renders a short notice before diving into the "Name for the new development store" prompt, because "the developer asked to run `app dev`, not to create a store" [3]. The store picker's "Create a new dev store" choice remains unprompted, as intent is already expressed there.

For consistency, `store create dev` also gains `static examples`, matching every sibling `shopify store` command (`auth`, `list`, `open`, `info`, `execute`, `create preview`, `delete`). Since the command is hidden, only the oclif manifest changes, not the README or docs data [4].

$ ls shopify/reviews/ # the step-back reads

the week in review CLI adds subscription migration commands the month in review CLI 4.6/4.7 hardens auth, trims startup, rewrites E2E ergonomics
Topics: JavaScript Full archive →

Quick answers

What shipped in Shopify on September 3, 2026?
Shopify CLI's interactive dev store creation now prompts for demo data, and the `--with-demo-data` flag becomes tri-state `--demo-data`. In total, 6 commits, 3 pull requests, and 1 releases landed.
Who contributed to Shopify on September 3, 2026?
2 developers shipped this update, including nickwesselman and Ariel Caplan.
What were the notable Shopify updates?
Ask about demo data when creating a dev store interactively, Ask about demo data when creating a dev store interactively, and Explain the empty-organization store creation prompts in app dev.
♥

$ log Shopify --recent

shopify store list gains server-side type filtering 5 shipped Filter store list by type, server-side 3 shipped Shopify CLI adds subscription migration list command 14 shipped Two Shopify CLI prompts make their unexpected appearances visible 13 shipped

$ log --all # elsewhere on the wire

Meta React Native adds Stable API guards to renderer attributed string FastAPI & Pydantic Pydantic fixes Mypy plugin crash, tightens datetime constraints

$ ls showcases/

Rails Django Laravel Node.js Go Vercel Vue.js Kubernetes HashiCorp Arch Linux Linux Anthropic

$ init your-desk

RepoJournal can write one of these for any repo you care about. Sign in with GitHub, pick your repos and sources, and your desk gets a wire like this one every morning.