The version 6.10.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 eslint-plugin-react.
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.
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).
Version 6.10.0 of eslint-plugin-react just got published.
The version 6.10.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 eslint-plugin-react. 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
v6.10.0Added
forbid-foreign-prop-typesrule (#696 @iancmyers)void-dom-elements-no-childrenrule (#709 @lencioni)forbid-elementsrule (#887 @kentor)noSortAlphabeticallyoption tojsx-sort-props(#541 #786 @markus101)whenoption tojsx-max-props-per-line(#878 @kentor)nextPropstoprop-types(#814)Fixed
require-default-propscrash (#1029)require-default-propsrule when using Flow type from assignment (#1043 @wyze @CarlRosell)style-prop-objectto not warn with explicitnullorundefined(#812 @ljharb)no-unused-prop-typesprops detection in stateless components (#885 @BarryThePenguin)display-namefalse positive withdocument.createElement(#996 @jomasti)Changed
Commits
The new version differs by 49 commits .
83d4c4bUpdate CHANGELOG and bump versionee144d6Merge pull request #890 from kentor/forbid-elements3e2421eMerge pull request #946 from BarryThePenguin/no-unused-prop-types-in-jsx3b25a3bMerge pull request #882 from kentor/jsx-max-props-per-line-updates54abb8bMerge pull request #1055 from iancmyers/icm-forbid-foreign-prop-type0b25b66Add forbid-foreign-prop-types rulec586273Merge pull request #1062 from dguo/patch-28e207b8Fix no-array-index-key typod884a98Add new rule: forbid-elementsc97dd0fMerge pull request #1051 from yannickcr/void-dom-elements-no-childrena84d5f5jsx-max-props-per-line: Use json format in docs9af8d25fix commentsd5c3e91detect used props in jsxb52f3b8jsx-max-props-per-line: Add additional test casesb485e28jsx-max-props-per-line: AddwhenoptionThere are 49 commits in total. See the full diff.
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: