The devDependency 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.
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
The devDependency react-redux was updated from
5.1.1to6.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
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
withRefoption toconnecthas been replaced withforwardRef. If{forwardRef : true}has been passed toconnect, adding a ref to the connected wrapper component will actually return the instance of the wrapped component. (Known issue: Redux Form currently relies onwithRef.)Passing
storeas a prop to a connected component is no longer supported. Instead, you may pass a customcontext={MyContext}prop to both<Provider>and<ConnectedComponent>. You may also pass{context : MyContext}as an option toconnect.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 includeconnected-react-routerandreact-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
nullas a valid plain object prototype inisPlainObject()(#1075 by @rgrove)Commits
The new version differs by 17 commits ahead by 17, behind by 3.
581ece46.0.09062722Upgrade a bunch of deps.7564f73Fix bad URL generationcf11a25Add new "Why use React-Redux?" page (#1097)ce17d0cUpdate Docusaurus and docs URLs (#1096)f0840f16.0.0-beta.36a2e878Forgot to rebuild the lockfile.dba598bAdd connectAdvanced() tests (#1079)1dc56caRe-enable "should throw if not in context" test8987de0Treatnullas a valid plain object prototype inisPlainObject()(#1075)59aaba5Relax React peer dep back to 16.47496b916.0.0-beta.11a92b56npm audit fix0c048f0Use Prettier (#1071)85fb553Use 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](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: