Upgrading Spree

Spree ships an upgrade flow that bundles three steps into one command:

1. bundle update — bump the Spree gems in your Gemfile.lock
2. db:migrate — apply migrations from the new gem version (after copying them in via spree:install:migrations)
3. bin/rake spree:upgrade — run version-specific data backfills shipped in each release

Use spree upgrade in development and bundle exec rake spree:upgrade in your deploy pipeline (production runs only the third step; bundle install + db:migrate are part of your platform's deploy flow).

Classic Rails apps (Spree gems in a plain Rails app, no Docker/CLI — typical pre-5.4) run the same three steps natively from the app root; the CLI flags map to env vars on the rake task (--plan → DRY_RUN=1, --step → STEP=<id>, --to → TO=<version>):

bundle update spree spree_core spree_api spree_admin spree_emails   # plus any spree_* extensions
bin/rake spree:install:migrations && bin/rails db:migrate
DRY_RUN=1 bin/rake spree:upgrade   # plan first
bin/rake spree:upgrade             # then run the data backfills