Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
b179a5b to
30ad26e
Compare
|
We detected some changes at Caution DO NOT create changesets for features which you do not wish to be included in the public changelog of the next CLI release. |
30ad26e to
97a6535
Compare
97a6535 to
09f967a
Compare
|
/snapit |
|
🫰✨ Thanks @dmerand! Your snapshot has been published to npm. Test the snapshot by installing your package globally: npm i -g --@shopify:registry=https://registry.npmjs.org @shopify/cli@0.0.0-snapshot-20260401235335Caution After installing, validate the version by running |
| return new AbortError( | ||
| `No stored app authentication found for ${store}.`, | ||
| 'To create stored auth for this store, run:', | ||
| storeAuthCommandNextSteps(store, '<comma-separated-scopes>'), |
There was a problem hiding this comment.
couldn't we pass the scopes here and build the full command?

What
Improve the
shopify store authandshopify store executeUX around authentication, verification, and recovery.This changes the
store authoutput to follow the existingshopify authstyle more closely, makes auth and re-auth commands easier to follow from error states, and updates the help text to describestore authas store-command auth rather thanstore execute-specific auth.Why
These changes follow the feedback collected in the Store execute friction doc:
https://docs.google.com/document/d/1Hwo9kFlIrEitsvS7i27q179_TiMbE9YNRZmn-j77G7s/edit?tab=t.0
The current flow has a few sources of friction:
store authoutput still reads like a bespoke flow instead of matching the CLI's auth conventionsstore authtoo closely tostore executeHow
store authhappy-path output to login-style completion linesTesting
shopify store auth --store <store> --scopes read_products