# Migrating from 0.6 to 1.0
1.0 is a security and correctness release. Most apps need four mechanical changes (requirements, toast provider, form actions used with `useFormAction`, native-form schemas); the rest are behaviour changes to review.
Projects that stay on `^0.6.0` are not affected: npm never installs a new major version on its own.
## 1. Requirements
| | 0.6 | 1.0 |
|---|---|---|
| Next.js | 14–16 | 15 or 16 (App Router) |
| React | 18 or 19 | 19 |
| Zod | bundled dependency | peer dependency: `npm install zod` |
| sonner | required by the hooks | not required (toast adapter) |
| react-hook-form, @hookform/resolvers | required by `/hooks` | optional, `>= 7.55` and `>= 5.1`, only for `/hooks/form` |
| TypeScript | any 5.x | 5.4 or later |
## 2. Toasts: add `ActionForgeProvider`, remove `ToastRestorer`
The hooks no longer import sonner. Pass your toast function once, from a Client Component:
```tsx
"use client";
import { toast } from "sonner";
import { ActionForgeProvider } from "next-action-forge/hooks";
export function Providers({ children }: { children: React.ReactNode }) {
return {children};
}
```
Without it, toasts are skipped (with a one-time warning in development). `ToastRestorer` is removed: delete its import and element.
## 3. `useFormAction`: new import path, regular actions
```diff
- import { useFormAction } from "next-action-forge/hooks";
+ import { useFormAction } from "next-action-forge/hooks/form";
```
`useFormAction` now sends the form values as an object to a regular action. Every action used with it changes from `.formAction()` to `.action()`:
```diff
export const updateUser = adminClient
.inputSchema(UpdateUserSchema)
- .formAction(async (input, context) => { … });
+ .action(async (input, context) => { … });
```
Passing a `.formAction()` is now a type error, and at runtime it answers `INVALID_FORM_DATA`. Booleans, numbers and dates arrive with their real types, so schemas written for the old string conversion keep working. Also:
- Field types still come from `defaultValues` (fields like `z.coerce.number()` stay numbers), and an action chosen at runtime (`isEdit ? updateUser : createUser`) keeps working. Explicit generics are now `useFormAction`.
- `transformData(values)` returns the action input (it returned FormData).
- `actionState` is `undefined` until the first submit (it started as `{ success: true, data: undefined }`); `result` holds the same `ActionResult` as `useServerAction`.
- A `FileList` from `register("file")` is sent as `File[]`.
## 4. Native forms: `.formAction()` no longer guesses types
`.formAction()` is for `