Spree 1.2.0 introduces some fairly major changes in the basic architecture of Spree, as well as minor alterations and bugfixes.
Due to the long development cycle of Spree 1.2 in parallel with continuing development of the 1.1 branch, there may be features released in 1.2 that are already present in 1.1.
There were two major topics addressed within this release of Spree: custom authentication and better checkout customization.
The first was the ability to use Spree in conjunction with an application that already provided its own way to authenticate users. Due to how Spree was architected in the past, this was not as easy as it could have been. In this release of Spree, the auth component of Spree has been removed completely and placed into a separate extension called spreeauthdevise. If you wish to continue using this component of Spree, you will need to specify this extension as a dependency in your Gemfile. See [Issue
The checkout process has always been hard to customize within Spree, and that has generated complaints in the past. We are pleased to report in the 1.2 release of Spree that this has been substaintially easier with a new checkout DSL that allows you to re-define the checkout steps in a simple manner. For more information about this, please see [Issue
Along with these two major issues, there were also a ton of minor improvements and bug fixes, explained in detail below.
Authentication is disabled by default within Spree as of this release, with the application supposed to be providing its own authentication. If you are upgrading an existing Spree installation or just want it to work, you can achieve the behaviour of a 1.1 installation by adding “spreeauthdevise” to your Gemfile.