chore(website): update docs for new status logic

Author: TheEdoRan

website/docs/execute-actions/hooks/useaction.md

@@ -77,11 +77,9 @@ As you can see, here we display a greet message after the action is performed, i
 - `isIdle`: true if the action status is `idle`.
 - `isTransitioning`: true if the transition status  from the `useTransition` hook used under the hood is `true`.
 - `isExecuting`: true if the action status is `executing`.
-- `isPending`: same as `isExecuting` (deprecated).
+- `isPending`: true if the action status is `executing` or `transitioning`.
 - `hasSucceeded`: true if the action status is `hasSucceeded`.
 - `hasErrored`: true if the action status is `hasErrored`.
 - `hasNavigated`: true if a `next/navigation` function was called inside the action.
 
-The `executing` status and `isExecuting` shorthand property include the transition state.
-
 Explore a working example [here](<https://github.com/TheEdoRan/next-safe-action/tree/main/apps/playground/src/app/(examples)/hook>).

website/docs/execute-actions/hooks/useoptimisticaction.md

@@ -131,7 +131,7 @@ export default function TodosBox({ todos }: Props) {
 - `isIdle`: true if the action status is `idle`.
 - `isTransitioning`: true if the transition status  from the `useTransition` hook used under the hood is `true`.
 - `isExecuting`: true if the action status is `executing`.
-- `isPending`: same as `isExecuting` (deprecated).
+- `isPending`: true if the action status is `executing` or `transitioning`.
 - `hasSucceeded`: true if the action status is `hasSucceeded`.
 - `hasErrored`: true if the action status is `hasErrored`.
 - `hasNavigated`: true if a `next/navigation` function was called inside the action.

website/docs/migrations/v7-to-v8.md

@@ -92,10 +92,6 @@ const result = await boundAction(input);
 
 The deprecated `executeOnMount` hook functionality has been removed in v8. Server Actions should be used only for mutations, so it doesn't make sense to execute them on mount. Or at least, it shouldn't be a common case and, above all, a library job. If you still need to do it, just use `useEffect()` to trigger the execution, however you want.
 
-### 🔄 Deprecation of `isPending` shorthand status property
-
-The `isPending` shorthand status property is now deprecated, and will be removed in a future version. Having both `isExecuting` and `isPending` properties is a bit confusing, so now both the `isExecuting` property and `"executing"` status value include the transition state of the action execution. `isPending` right now is just an alias for `isExecuting`.
-
 ### ✨ Type-checked metadata
 
 This is a big improvement in type safety over v7. Metadata is now statically type-checked when passed to actions. So, now if you forget to pass the expected metadata shape, as defined by the `defineMetadataSchema` init option, you will get a type error immediately:
@@ -131,6 +127,10 @@ const action = actionClient
 );
 ```
 
+### ✨ Added `transitioning` status
+
+The `transitioning` status has been added to the hook result object. This status is set when the action has finished executing, but the transition is not yet complete. The transition state is handled by the [`useTransition()`](https://react.dev/reference/react/useTransition) React hook used under the hood in next-safe-action hooks.
+
 ### 🔄 Safe action result always defined
 
 The action result object is now always defined. This allows you to destructure it without the need to check if it's defined or not first: