one-dot-one-to-one-dot-two.md

title	section	order	hidden	description
Upgrading Spree from 1.1.x to 1.2.x	upgrades	15	true	This guide covers upgrading a 1.1.x Spree store, to a 1.2.x store.

1.1 to 1.2

Overview

This guide has been written from the perspective of a blank Spree 1.1.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 works within your 1.2.x store once this upgrade is complete. Typically, extensions that are compatible with this version of Spree will have a 1-2-stable branch.

Upgrade Spree

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

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

Run `bundle update spree`.

## Authentication dependency

In this release, the `spree_auth` component was moved out of the main set of
gems into an extension, called `spree_auth_devise`. If you want to continue using Spree's authentication, then you will need to specify this extension as a dependency in your `Gemfile`:

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

Run `bundle install` to install this extension.

### Rename current_user to current_spree_user

To ensure that Spree does not conflict with any authentication provided by the application, Spree has renamed its `current_user` variable to `current_spree_user`. You should make this change wherever necessary within your application.

Similar to this, any references to `@user` are now `@spree_user`.

## 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

This may copy over additional migrations from spree_auth_devise and run them as well.

## Read the release notes

For information about changes contained with this release, please read the [1.2.0 Release Notes](http://guides.spreecommerce.org/release_notes/spree_1_2_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.