Bug: react-hooks/exhaustive-deps false postive when use `isPending` in `useActionState`

[dislido]

React version: 19.0.0, eslint-plugin-react-hooks: 5.1.0

Steps To Reproduce

1. Create a useActionState value and use the third value in the return value
2. Use dispatch function in useEffect

Link to code example:

import type React from 'react';
import { useActionState, useEffect } from 'react';

export const Example: React.FC = () => {
  const [_, dispatch, _isPending] = useActionState(() => 0, 0);
  useEffect(() => {
    dispatch();
  }, []); // React Hook useEffect has a missing dependency: 'dispatch'. Either include it or remove the dependency array.

  const [_2, dispatch2] = useActionState(() => 0, 0);
  useEffect(() => {
    dispatch2();
  }, []); // ok
  return null;
};

The current behavior

React Hook useEffect has a missing dependency: 'query'. Either include it or remove the dependency array.

The expected behavior

No lint errors.

---

Only handled 2 elements.

react/packages/eslint-plugin-react-hooks/src/ExhaustiveDeps.js

Line 273 in 056073d

id.elements.length === 2 &&

[Sunilbasfore]

React Hook useEffect has a missing dependency: 'query'. Either include it or remove the dependency array.

[Sunilbasfore]

React Hook useEffect has a missing dependency: 'query'. Either include it or remove the dependency array.

[paztis]

I add additional info here:

Globally the rule is invalid on useEffect and useLayoutEffect
I can type this code that is totally valid:

const Component = ({currentValue, onValueChange}) => {

    useEffect(() => {
        onValueChange(currentValue)
    }, currentValue);
};

In this case I don't want to re-execute it if the onValueChange change but only if the currentValue change.

there's no problem to do this, at execution time it will be well the correct onValueChange function
This is true because as opposite to a useCallback, the useEffect inner function is recreated on each rendering. so all variable pointers inside are correctly point to the latest.

So the linter rule here report tons of false positive for me.
Because of this i didn't use your rule that is really useful for the useCallback and the useMemo

A good solution for me is to provide an option to disabe the scan of the useEffect and the useLayoutEffect.

you already have an option additionalHooks to add additional hooks scan
What I think is you may propose another option to disable some native hooks scan disabledHooks for example