The version 16.3.2 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.
It might be worth looking into these changes and trying to get this project onto the latest version of react.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notesv16.3.2
16.3.2 (April 16, 2018)
React
Improve the error message when passing null or undefined to React.cloneElement. (@nicolevy in #12534)
React DOM
Fix an IE crash in development when using <StrictMode>. (@bvaughn in #12546)
Fix labels in User Timing measurements for new component types. (@bvaughn in #12609)
Improve the warning about wrong component type casing. (@nicolevy in #12533)
Improve general performance in development mode. (@gaearon in #12537)
Improve performance of the experimental unstable_observedBits API with nesting. (@gaearon in #12543)
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).
Version 16.3.2 of react was just published.
The version 16.3.2 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.
It might be worth looking into these changes and trying to get this project onto the latest version of react.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v16.3.216.3.2 (April 16, 2018)
React
null
orundefined
toReact.cloneElement
. (@nicolevy in #12534)React DOM
<StrictMode>
. (@bvaughn in #12546)unstable_observedBits
API with nesting. (@gaearon in #12543)React Test Renderer
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: