Upgrading Spree from 1.0.x to 1.1.x

Overview

This guide covers upgrading a 1.0.x Spree store, to a 1.1.x store. This guide has been written from the perspective of a blank Spree 1.0.x store with no extensions.

If you have extensions that your store depends on, you will need to manually verify that each of those extensions work within your 1.1.x store once this upgrade is complete. Typically, extensions that are compatible with this version of Spree will have a 1-1-stable branch.

Upgrade Rails

Spree 1.1 depends on any Rails 3.2 release afer Rails 3.2.9. Ensure that you have that dependency specified in your Gemfile:

gem 'rails', '~> 3.2.9'```

Along with this, you may have to also update your assets group in the Gemfile:

```ruby
group :assets do
  gem 'sass-rails',   '~> 3.2.5'
  gem 'coffee-rails', '~> 3.2.1'
  gem 'uglifier', '>= 1.0.3'
end

gem 'jquery-rails', '2.1.4'

For more information, please refer to the Upgrading Ruby on Rails guide.

Upgrade Spree

For best results, use the 1-1-stable branch from GitHub:

gem 'spree', github: 'spree/spree', branch: '1-1-stable'```

Run `bundle update spree`.

## Copy and run migrations

Copy over the migrations from Spree (and any other engine) and run them using
these commands:

    rake railties:install:migrations
    rake db:migrate

## Remove references to spree_api assets

Spree API no longer provides any asset files, so references to these must be removed from:

* app/assets/stylesheets/store/all.css
* app/assets/stylesheets/admin/all.css
* app/assets/javascripts/store/all.js
* app/assets/javascripts/admin/all.js

## Read the release notes

For information about what has changed in this release, please read the [1.1.0 Release Notes](http://guides.spreecommerce.org/release_notes/spree_1_1_0.html).

## Verify that everything is OK

Click around in your store and make sure it's performing as normal. Fix any deprecation warnings you see.