**Do you want to request a *feature* or report a *bug*?**
feature

**What is the current behavior?**
Using in my `package.json`:
```
    "eslint": "^6.0.0",
    "eslint-plugin-react-hooks": "^1.6.0",
```
Yarn emits:
```
warning " > eslint-plugin-react-hooks@1.6.0" has incorrect peer dependency "eslint@^3.0.0 || ^4.0.0 || ^5.0.0".
```

**What is the expected behavior?**
No warning.

AFAICT, there shouldn't be other change needed besides updating the peer dependency version in the `package.json`: https://eslint.org/docs/user-guide/migrating-to-6.0.0
so it looks like I could just ignore the warning, but I'd rather be sure the plugin is actually compatible with ESLint 6.0.0

**Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?**
n/a
use42();
      useHook();
      use_hook();
      React.useState();
    `,
    `
      // Regression test for the popular "history" library
      const {createHistory, useBasename} = require('history-2.1.2');
      const browserHistory = useBasename(createHistory)({
        basename: '/',
      });
    `,
    `
      // Regression test for some internal code.
      // This shows how the "callback rule" is more relaxed,
      // and doesn't kick in unless we're confident we're in
      // a component or a hook.
      function makeListener(instance) {
        each(pixelsWithInferredEvents, pixel => {
          if (useExtendedSelector(pixel.id) && extendedButton) {
            foo();
          }
        });
      }
    `,
    `
      // Regression test for incorrectly flagged valid code.
      function RegressionTest() {
        const foo = cond ? a : b;
        useState();