The version 15.6.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of react-addons-test-utils.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notesv15.6.0
15.6.0 (June 13, 2017)
React
Downgrade deprecation warnings to use console.warn instead of console.error. (@flarnie in #9753)
Add a deprecation warning for React.createClass. Points users to create-react-class instead. (@flarnie in #9771)
Add deprecation warnings and separate module for React.DOM factory helpers. (@nhunzaker in #8356)
Warn for deprecation of React.createMixin helper, which was never used. (@aweary in #8853)
React DOM
Add support for CSS variables in style attribute. (@aweary in #9302)
Add support for CSS Grid style properties. (@ericsakmar in #9185)
Fix bug where inputs mutated value on type conversion. (@nhunzaker in #9806)
Fix issues with onChange not firing properly for some inputs. (@jquense in #8575)
Fix bug where controlled number input mistakenly allowed period. (@nhunzaker in #9584)
Fix bug where performance entries were being cleared. (@chrisui in #9451)
React Addons
Fix AMD support for addons depending on react. (@flarnie in #9919)
Fix isMounted() to return true in componentWillUnmount. (@mridgway in #9638)
Fix react-addons-update to not depend on native Object.assign. (@gaearon in #9937)
Remove broken Google Closure Compiler annotation from create-react-class. (@gaearon in #9933)
Remove unnecessary dependency from react-linked-input. (@gaearon in #9766)
Point react-addons-(css-)transition-group to the new package. (@gaearon in #9937)
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
greenkeeper[bot]
commented
7 years ago
Version 15.6.0 of react-addons-test-utils just got published.
The version 15.6.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of react-addons-test-utils. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
v15.6.015.6.0 (June 13, 2017)
React
console.warninstead ofconsole.error. (@flarnie in #9753)React.createClass. Points users tocreate-react-classinstead. (@flarnie in #9771)React.DOMfactory helpers. (@nhunzaker in #8356)React.createMixinhelper, which was never used. (@aweary in #8853)React DOM
styleattribute. (@aweary in #9302)onChangenot firing properly for some inputs. (@jquense in #8575)React Addons
react. (@flarnie in #9919)isMounted()to returntrueincomponentWillUnmount. (@mridgway in #9638)react-addons-updateto not depend on nativeObject.assign. (@gaearon in #9937)create-react-class. (@gaearon in #9933)react-linked-input. (@gaearon in #9766)react-addons-(css-)transition-groupto the new package. (@gaearon in #9937)Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: