3.0 to 3.1

Upgrade Rails
For this Spree release, you will need to upgrade your Rails version to at least 4.2.6.
1
gem 'rails', '~> 4.2.6'
Copied!
Upgrade Spree
For best results, use the spree gem in version 3.1.x:
1
gem 'spree', '~> 3.1.0.rc1'
Copied!
Run bundle update spree.
Copy and run migrations
Copy over the migrations from Spree (and any other engine) and run them using these commands:
1
rake railties:install:migrations
2
rake db:migrate
Copied!
Spree Auth Devise & Spree Gateway
If you are using Spree Gateway and/or Spree Auth Devise you should also upgrade them:
1
gem 'spree_auth_devise', '~> 3.1.0.rc1'
2
gem 'spree_gateway', '~> 3.1.0.rc1'
Copied!
For Spree Auth Devise run installer:
1
rails g spree:auth:install
Copied!
(you don't have to override config/initializers/devise.rb)
Additional information
Make sure to v1 namespace custom rabl templates & overrides.
If your rabl templates reference others with extend you'll need to add the v1 namespace.
For example:
1
extends 'spree/api/zones/show'
Copied!
Becomes:
1
extends 'spree/api/v1/zones/show'
Copied!
Remove Spree::Config.check_for_spree_alerts
If you were disabling the alert checks you'll now want to remove this preference as it's no longer used.
Read the release notes
For information about changes contained within this release, please read the 3.1.0 Release Notes.
Verify that everything is OK
Run your test suite, click around in your store and make sure it's performing as normal. Fix any deprecation warnings you see.

3.1 to 3.2

2.3 to 2.4

Last modified 2mo ago

Copy link

Contents

Upgrade Rails

Upgrade Spree

Copy and run migrations

Spree Auth Devise & Spree Gateway

Additional information

Make sure to v1 namespace custom rabl templates & overrides.

Remove Spree::Config.check_for_spree_alerts

Read the release notes

Verify that everything is OK