New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update react-redux to the latest version 馃殌 #614

merged 3 commits into from Dec 6, 2018


None yet
2 participants

greenkeeper bot commented Dec 5, 2018

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鈥檛 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.



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鈥檛 help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper bot 馃尨

@greenkeeper greenkeeper bot added the greenkeeper label Dec 5, 2018

@lmorchard lmorchard merged commit d17b6d0 into master Dec 6, 2018

1 check passed

ci/circleci: build_and_test Your tests passed on CircleCI!

@greenkeeper greenkeeper bot deleted the greenkeeper/react-redux-6.0.0 branch Dec 6, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment