Update dependency react-hook-form to v7.85.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
react-hook-form (source)	7.72.0 → 7.85.0

---

Release Notes

react-hook-form/react-hook-form (react-hook-form)

v7.85.0

Compare Source

Added

• Support <Activity />

Fixed

• getFieldState error resolution from a field path
• useWatch discarding useForm({ defaultValues }) in favor of its own defaultValue before the form mounts
• setValue emitting a duplicate values state notification for fields without a native input ref
• Stale render re-creating a field array path vacated by an array action
• useFieldArray root-level error (errors.name.root) being lost on append/prepend/insert/remove
• min/max validation being skipped for valueAsDate fields

v7.84.0

Compare Source

v7.83.0: Version 7.83.0

Compare Source

⚡ Improvements

• enhance getEventValue to handle file inputs (#​13289)
• type perf: improve TypeScript performance with a hard cap at 10 levels of recursive type depth (#​13529)
• type perf: improve type performance (#​13528)

🐞 Fixes

• fix: clear internal errors state on argument-less clearErrors() (#​13613)
• fix: preserve dirtyFields reference stability (#​13612)
• fix: old checkbox/radio elements polluting internal field state (#​13080)
• fix(useController): re-subscribe onChange/onBlur when control changes (#​13603)
• fix(types): allow validation messages to be defined even if their related value is undefined (#​13287)

v7.82.0

Compare Source

Added

• Opt-in delayError option for setValue to delay validation error updates

Fixed

• Expose resetDefaultValues through form context
• setValue with shouldDirty not updating dirty state correctly when the form is disabled
• Preserve dirtyFields boolean values for registered array fields
• Restore FieldArray component export

Performance

• Improve getDirtyFields performance, especially for larger forms and deeply nested values

v7.81.0

Compare Source

v7.80.0: Version 7.80.0

Compare Source

🧄 feat: disable useFieldArray fields (#​13535)

const { fields } = useFieldArray({ disabled: true });
fields[0].disabled; // contains disabled props

🛺 perf: make rhf more performant (#​13524)
🐞 fix(deepEqual): empty array and empty plain object should not be equal (#​13533)

thanks to @​JSap0914

v7.79.0

Compare Source

Added

• disabled option to useFieldArray

Fixed

• Controller onChange promise return type
• deepEqual false positives with shared object references
• shouldUseNativeValidation behavior for radio groups
• createFormControl stability with fast refresh in dev mode
• StrictMode value preservation during remount
• formState.errors reactivity with React compiler

v7.78.0

Compare Source

Fixed

• Recover Controller fields after reset without rerender (RN issue #​13455)
• useFormState().isDirty race with async resolver in onChange mode
• Use reactive values prop over defaultValues when shouldUnregister is true
• deepEqual for empty non-plain objects

Types

• Update dirtyFields typing for field arrays with undefined entries

v7.77.0

Compare Source

Added

• resetDefaultValues API

Fixed

• Stale isDirty in subscribe payload after reset(..., { keepValues: true })
• Preserve values with shouldUnregister
• Inconsistent reset({}) behavior requiring double-call to take effect
• FieldArray errors overriding nested fields

Security

• Harden get() against prototype-path traversal (__proto__ / constructor / prototype)

Performance

• Bundle size reduction

v7.76.1

Compare Source

Fixed

• Revert notify all matching field-array roots on nested setValue updates
• Revert treat NaN as empty when valueAsNumber is true in validateField
• setValues pass options parameter through to enable validation
• setValues emit whole-form change without stale name/type

Performance

• setValues skip redundant per-field deep clones
• setValues thread skipClone through setFieldValue

v7.76.0

Compare Source

Added

• Improve isDirty sync with dirtyFields state

Fixed

• Preserve formState.defaultValues when useFieldArray and watch are used together
• Preserve nested resolver field-array errors in trigger()
• Notify all matching field-array roots on nested setValue updates
• useFieldArray remove leaves array with empty object when using values prop
• Preserve reset values for conditionally mounted Controller fields with shouldUnregister
• Propagate setValues updates to mounted Controller fields
• Native validation tooltip suppression caused by duplicate submit-error focus
• append({ obj: null }) silently replaced by defaultValues after remove()
• Errors state when using form-level validation
• isValidating reactivity when validatingFields is not subscribed

v7.75.0

Compare Source

Added

• Improve getDirtyFields to prune empty fields
• TypeScript 6.0 support

Fixed

• Include setValues in FormProvider context value
• Preserve watch updates on field array unmount
• Prevent useWatch re-render when unrelated field validation occurs
• Recompute isDirty after re-registering a previously unregistered field

v7.74.0

Compare Source

Added

• setValues API

Fixed

• Preserve previous field value when useController name changes
• Handle null parent when unregistering nested field
• Treat NaN as empty when valueAsNumber is true in validateField

v7.73.1

Compare Source

Fixed

• Reverted setValues that was accidentally included in patch; fix build to exclude test files

v7.72.1

Compare Source

Fixed

• Prevent setValue with shouldDirty from polluting unrelated dirty fields
• Memoize control in HookFormControlContext to prevent render conflicts
• isNameInFieldArray should check all ancestor paths for nested field arrays
• formState.isValid incorrect on Controller re-mount

---

Configuration

📅 Schedule: (in timezone America/New_York)

• Branch creation
  • Between 12:00 AM and 11:59 PM (* 0-23 * * *)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: react-beautiful-dnd@13.1.1
npm error Found: react@19.2.4
npm error node_modules/react
npm error   peer react@">=16.8.0" from @emotion/react@11.14.0
npm error   node_modules/@emotion/react
npm error     peer @emotion/react@"^11.0.0-rc.0" from @emotion/styled@11.14.1
npm error     node_modules/@emotion/styled
npm error       peerOptional @emotion/styled@"^11.3.0" from @mui/lab@7.0.1-beta.23
npm error       node_modules/@mui/lab
npm error         @mui/lab@"^7.0.1-beta.19" from the root project
npm error       4 more (@mui/material, @mui/styled-engine, @mui/system, the root project)
npm error     peerOptional @emotion/react@"^11.5.0" from @mui/lab@7.0.1-beta.23
npm error     node_modules/@mui/lab
npm error       @mui/lab@"^7.0.1-beta.19" from the root project
npm error     5 more (@mui/material, @mui/styled-engine, @mui/system, ...)
npm error   peer react@">=16.8.0" from @emotion/styled@11.14.1
npm error   node_modules/@emotion/styled
npm error     peerOptional @emotion/styled@"^11.3.0" from @mui/lab@7.0.1-beta.23
npm error     node_modules/@mui/lab
npm error       @mui/lab@"^7.0.1-beta.19" from the root project
npm error     peerOptional @emotion/styled@"^11.3.0" from @mui/material@7.3.9
npm error     node_modules/@mui/material
npm error       peer @mui/material@"^7.3.9" from @mui/icons-material@7.3.9
npm error       node_modules/@mui/icons-material
npm error         @mui/icons-material@"^7.3.5" from the root project
npm error       2 more (@mui/lab, the root project)
npm error     3 more (@mui/styled-engine, @mui/system, the root project)
npm error   29 more (@emotion/use-insertion-effect-with-fallbacks, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^16.8.5 || ^17.0.0 || ^18.0.0" from react-beautiful-dnd@13.1.1
npm error node_modules/react-beautiful-dnd
npm error   react-beautiful-dnd@"^13.1.1" from the root project
npm error
npm error Conflicting peer dependency: react@18.3.1
npm error node_modules/react
npm error   peer react@"^16.8.5 || ^17.0.0 || ^18.0.0" from react-beautiful-dnd@13.1.1
npm error   node_modules/react-beautiful-dnd
npm error     react-beautiful-dnd@"^13.1.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-08-20T21_56_47_091Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-08-20T21_56_47_091Z-debug-0.log

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
adminv2	Ready	Preview	Aug 20, 2026 10:13pm