**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
console.log(state3);
            console.log(state4);
            console.log(state5);
            console.log(state6);
            mySetState();
            myDispatch();
            // Not sure; assume dynamic
            maybeSetState();
            maybeDispatch();
          }, [
            // Dynamic
            state1, state2, state3, state4, state5, state6,
            maybeRef1, maybeRef2,
            // Not sure; assume dynamic
            mySetState, myDispatch,
            maybeSetState, maybeDispatch
            // In this test, we don't specify static deps.
            // That should be okay.
          ]);
        }
      `,
    },
    {
      code: `
        function MyComponent({ maybeRef2 }) {
          const definitelyRef1 = useRef();
          const definitelyRef2 = useRef();
          const maybeRef1 = useSomeOtherRefyThing();
          const [state1, setState1] = useState();
          const [state2, setState2] = React.useState();