fix(deps): update dependency @hookform/resolvers to v5

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@hookform/resolvers (source)	^3.10.0 → ^5.0.0

---

Release Notes

react-hook-form/resolvers (@​hookform/resolvers)

v5.2.2

Compare Source

Bug Fixes

• zod: fix output type for Zod 4 resolver (#​803) (e95721d)

v5.2.1

Compare Source

Bug Fixes

• discriminated union for zod v4 mini (#​784) (49a0d7b)
• zod v4 peer deps (#​798) (2d28e6a)
• zod: fix output type for Zod 4 resolver (#​801) (bc09647)

v5.2.0

Compare Source

Features

• ajv: add ajv-formats for ajvResolver (#​797) (f040039)

v5.1.1

Compare Source

Bug Fixes

• zod peer dep issue (#​780) (79cd8b2)

v5.1.0

Compare Source

Features

• support Zod 4, Zod v4 mini, and retains compatibility with Zod v3. (#​777) (8d083bd)

v5.0.1

Compare Source

Bug Fixes

• relax version constraint for react-hook-form 7.55.0 → ^7.55.0 (#​758) (6e88393)

v5.0.0

Compare Source

Features

• infer input/output types from schema (#​753) (6124c59)

BREAKING CHANGES

• Requires react-hook-form@​7.55.0 or higher

Before
Prior to V5, some projects used manual types like

useForm<FormValues>();

After
With V5, the correct approach is:

useForm<Input, Context, Output>();
useForm<FormInputValues, Context, FormOutputValues>();

This update enables distinct outputs when utilizing features like transform from validation libraries.

ℹ️ The best approach is to let the types be inferred from your schema, rather than manually defining them.

v4.1.3

Compare Source

Bug Fixes

• escape square brackets in field name regex pattern (#​752) (50dd4ad)

v4.1.2

Compare Source

Bug Fixes

• standard-schema: move @​standard-schema/utils to dependencies (#​748) (ded1746)

v4.1.1

Compare Source

Bug Fixes

• standard-schema: Propertly handle object path segments (#​746) (8ffada0)

v4.1.0

Compare Source

Features

• automatically infer values from schema (#​739) (caaff8d)

v4.0.0

Compare Source

Bug Fixes

• add support for names option (#​713) (985c48d)
• arktypeResolver: resolve type error when schema is defined from an ArkType scope (#​732) (3233667)
• handle raw: true option to pass form submission values correctly (#​733) (7807f95)
• validateFieldsNatively: handle undefined object when reading 'refs' (#​734) (3da2054)

Features

• ajv: Keep original validation type while using errorMessage (#​728) (5030a59)
• effectResolver: returns either all errors or only the first one based on criteriaMode (#​737) (12d7d8e)
• standard-schema: add standard-schema resolver (#​738) (b75a95a)

BREAKING CHANGES

• ajv: The AJV Resolver now unwraps the errorMessage object to return the original error types. This update may introduce breaking changes to your projects.

---

Configuration

📅 Schedule: Branch creation - "before 10am on friday" in timezone Europe/London, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

Open in Overmind ↗

---

model|risks_v6
✨Encryption Key State Risk ✨KMS Key Creation

🔥 Risks

Tip

✔ No observations recorded

We weren't able to record any observations for this change. This may indicate limited connectivity between affected items - check that your mapped resources include the expected dependencies.

---

---

💥 Blast Radius

Items 0

Edges 0

[github-actions]

✅ Auto-Approved

---

🟢 Decision

Auto-approved: All safety checks passed

---

🔥 Risks Summary

High 0 · Medium 0 · Low 0

---

View full analysis in Overmind ↗