UPGRADE.md

1.3.3 to 1.3.4 (January 9, 2017)

Nothing to do.

1.3.2 to 1.3.3 (November 4, 2016)

Important:

• If you are seeing the error "Uncaught Invariant Violation: You have provided a history object created with history v3.x. This version of React Router is not compatible with v3 history objects. Please use history v2.x instead." you need to double-check your dependencies and if you are using the history module, you need to set that to use version 2.1.2. This is because ReactRouter is incompatible with history versions >= 3.x.x and 2.1.2 is the latest 2.x.x release.

1.3.1 to 1.3.2 (November 4, 2016)

Nothing to do.

1.3.0 to 1.3.1 (August 22, 2016)

Nothing to do.

1.2.2 to 1.3.0 (August 8, 2016)

Important:

• Due to React's new "Unkonwn Prop" warning (see https://facebook.github.io/react/warnings/unknown-prop.html) all spIf and spBind element attributes should be prefixed with data-. I.e. spIf should be data-spIf and spBind should be data-spBind. Adding the data- prefix will remove the the "Unkonwn Prop" warnings and guarantee future compatibility.

1.2.1 to 1.2.2 (June 30, 2016)

Nothing to do.

1.2.0 to 1.2.1 (May 5, 2016)

Nothing to do.

1.1.1 to 1.2.0 (May 5, 2016)

Important:

• We've updated to React v15 and React-Router v2. So when upgrading, please see the React v15 upgrade guide and the React-Router v2 upgrade guide.

1.1.1 to 1.1.2 (Apr 26, 2016)

Nothing to do.

1.1.0 to 1.1.1 (Apr 13, 2016)

Nothing to do.

1.0.0 to 1.1.0 (Mar 31, 2016)

Notice:

• The UserComponent and UserField components have been deprecated and will be removed in the future. So if you are using these, please take a look at our new context support instead (see docs). It makes integrating user data into your components much easier.

0.5.0 to 1.0.0 (Mar 1, 2016)

Breaking:

• The logout request has changed from doing a GET to a POST request. So if you're using the express-stormpath module you'll have to assure that you're running at least express-stormpath version 3.0.0.

Notice:

• The LogoutLink previously redirected the user to the path of the LogoutRoute. This has changed. The LogoutRoute is in fact no longer needed. So instead of redirecting to the LogoutRoute path, the LogoutLink will take care of doing the logout itself.