v4.3.0

• Adds per-instance memoization API. If your mapStateToProps or mapDispatchToProps returns a function, that function will be used instead for the given component instance. Most apps never need this, but it can be handy for custom memoization logic in apps with large component trees. It can bring significant performance improvements when used together with Reselect. (#279, 7ee928b, #179)

v4.2.1

• Bump Lodash to 4.2.0 (reduxjs/redux#1346, reduxjs/redux#1349)

v4.2.0

• isPlainObject that we use internally is now outsourced to Lodash 4.1 (reduxjs/redux#1339). Note that this does not mean we depend on Lodash itself. We only use a tiny module from it. We also use the same module in Redux >= 3.2.0.

v4.1.2

• Don't depend on console or console.error (reduxjs/redux#1311, 208efae)
• Remove warning from the production builds (208efae)

v4.1.1

• Adds loose-envify as a dependency to fix builds for Browserify users. (#1304 & #1306)

v4.1.0

• For Browserify users, Redux should now be properly envified without extra configuration (#274)

v4.0.6

• Fixes a regression on IE8. (#232, #233, caae2e1, https://phabricator.babeljs.io/T2817)

v4.0.5

• Avoids unnecessary recalculation of props for components that don't specify mapStateToProps (6c504b9#commitcomment-15145082, 04693ca)

v4.0.4

• Avoids use of Object.defineProperty() to prevent errors in IE8 (#227)

v4.0.3

• Fixes a bug that caused the props of connected components to not updated during a hot update with something like React Hot Loader. Internally, it involved moving the memoized calculations from shouldComponentUpdate() into more appropriate places such as componentWillReceiveProps(), handleChange(), and render(). (#224, #225)