Update react-redux to the latest version 🚀

[greenkeeper]

The dependency react-redux was updated from 5.1.1 to 6.0.0.

This version is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

---

Release Notes for v6.0.0

🎉 This is our first big release supporting the new Context API added in React 16.4! No more blocked updates!

As such, we now require React 16.4 or higher. Make sure to update your version when updating to this release.

This work has been mostly lead by @cellog and @markerikson, with special guest appearances by yours truly and a whole cast of helpful reviewers.

Breaking Changes

• The withRef option to connect has been replaced with forwardRef. If {forwardRef : true} has been passed to connect, adding a ref to the connected wrapper component will actually return the instance of the wrapped component. (Known issue: Redux Form currently relies on withRef.)

• Passing store as a prop to a connected component is no longer supported. Instead, you may pass a custom context={MyContext} prop to both <Provider> and <ConnectedComponent>. You may also pass {context : MyContext} as an option to connect.

Behavior Changes

Any library that attempts to access the store instance out of legacy context will break, because we now put the store state into a <Context.Provider> instead. Examples of this include connected-react-router and react-redux-subspace. (The current implementation does also put the store itself into that same context. While accessing the store in context is not part of our public API, we will still try to make it possible for other libraries to access it, with the understanding that this could break at any time.)

Also, there is a behavior change around dispatching actions in constructors / componentWillMount. Previously, dispatching in a parent component's constructor would cause its children to immediately use the updated state as they mounted, because each component read from the store individually. In version 6, all components read the same current store state value from context, which means the tree will be consistent and not have "tearing". This is an improvement overall, but there may be applications that relied on the existing behavior.

Changes

• Use React.createContext() (#1000 by @cellog)
• Use Prettier (#1071 by @NMinhNguyen)
• Only run isValidElementType in development builds (#1069 by @alexreardon)
• Treat null as a valid plain object prototype in isPlainObject() (#1075 by @rgrove)
• Ensure connectAdvanced only re-renders if derived props change (#1079 by @epeli and @markerikson)

Commits

The new version differs by 17 commits ahead by 17, behind by 3.

• 581ece4 6.0.0
• 9062722 Upgrade a bunch of deps.
• 7564f73 Fix bad URL generation
• cf11a25 Add new "Why use React-Redux?" page (#1097)
• ce17d0c Update Docusaurus and docs URLs (#1096)
• f0840f1 6.0.0-beta.3
• 6a2e878 Forgot to rebuild the lockfile.
• dba598b Add connectAdvanced() tests (#1079)
• 1dc56ca Re-enable "should throw if not in context" test
• 8987de0 Treat null as a valid plain object prototype in isPlainObject() (#1075)
• 59aaba5 Relax React peer dep back to 16.4
• 7496b91 6.0.0-beta.1
• 1a92b56 npm audit fix
• 0c048f0 Use Prettier (#1071)
• 85fb553 Use React.createContext() by @cellog (#1000)

There are 17 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper bot 🌴

[Betree]

Require redux-form update. See redux-form/redux-form#4216

[greenkeeper]

• The dependency react-redux was updated from 5.0.7 to 6.0.1.

Update to this version instead 🚀

Release Notes for v6.0.1

This is a minor release with support for react-hot-loader and a few small bug fixes for edge cases.

While you're here, please stop by #1177 to see our roadmap for the next versions of React Redux. We are aware that performance is not so hot in 6.0. Short version: We put too much traffic on React's context API, which isn't really designed for high levels of reads and writes. We're looking to reduce that load and get performance back on track in a minor release, so there won't be backwards compatibility concerns. We have a new extensive benchmark suite to keep us on track and ensure we're not regressing on speed in the future.

And yes, we know about Hooks. Check out #1179.

Changes

• Fix for circular component object structures, such as Emotion styled components. (#1122 by @Andarist)
• Minor optimization: remove conditional (#1131 by @ericanderson)
• Ensure that component context prop really contains a React context (#1134 by @casdevs)
• react-hot-loader compatibility (#1168/#1137 by @theKashey)
• Upgrade to react-is v16.7.0 (#1174 by @nobezawa)

Commits

The new version differs by 35 commits.

• 162b81a 6.0.1
• d8a7ab5 Update build deps. Add React 16.8 tests.
• 6ad2b55 Remove --save option as it isn't required anymore (#1193)
• fac9ad1 Update Provider.md and quick-start.md (#1182)
• 9bf2375 Update Provider.md
• fcd5ed8 Update Provider.md
• c198249 Update react-router usage example (#1180)
• ab77450 Upgrade to react-is v16.7.0 (#1174)
• 0bf4e1f Remove duplicate line in connect api documents (#1173)
• 6e0a106 Updated: Support React-Hot-Loader compatibility (#1168)
• 63af52f Update accessing-store.md (#1163)
• 5199d9d Ensure that component prop 'context' really contains a React context … (#1134)
• e7661b3 Fix spacing issues (#1153)
• 75b90f9 Add / change docs about v6 (#1148)
• 5088345 Add connect() API doc (#1140)

There are 35 commits in total.

See the full diff