Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: react-hook-form/react-hook-form
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v7.71.1
Choose a base ref
...
head repository: react-hook-form/react-hook-form
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v7.71.2
Choose a head ref
  • 5 commits
  • 12 files changed
  • 6 contributors

Commits on Jan 26, 2026

  1. Configuration menu
    Copy the full SHA
    3adba2b View commit details
    Browse the repository at this point in the history

Commits on Feb 5, 2026

  1. Configuration menu
    Copy the full SHA
    0e04ad3 View commit details
    Browse the repository at this point in the history

Commits on Feb 8, 2026

  1. 🕵️‍♂️ fix: use DeepPartialSkipArrayKey for WatchObserver value parame…

    …ter (#13278)
    
    * fix: use DeepPartialSkipArrayKey for WatchObserver value parameter
    
    Fixes #13269
    
    Changes WatchObserver type to use DeepPartialSkipArrayKey instead of
    DeepPartial for the value parameter. This prevents unnecessary
    undefined injection when field values are arrays, like multi-value
    select inputs.
    
    Before: (string | undefined)[] | undefined
    After: string[] | undefined
    
    This provides more accurate type inference without breaking changes,
    as DeepPartialSkipArrayKey still handles optional fields correctly.
    
    * Update API contract for WatchObserver type change
    veeceey authored Feb 8, 2026
    Configuration menu
    Copy the full SHA
    319b3ed View commit details
    Browse the repository at this point in the history

Commits on Feb 11, 2026

  1. 🧹 fix(clearErrors): emit name signal for targeted field updates (#13280)

    When clearErrors is called with specific field name(s), the state
    emission now includes the 'name' property so that shouldSubscribeByName
    can properly filter updates. This prevents components subscribed to
    unrelated field names (with exact: true) from unnecessarily re-rendering.
    
    Fixes #13277
    
    Co-authored-by: Kai Gritun <kai@kaigritun.com>
    kaigritun and Kai Gritun authored Feb 11, 2026
    Configuration menu
    Copy the full SHA
    4933dcc View commit details
    Browse the repository at this point in the history

Commits on Feb 20, 2026

  1. 7.71.2

    bluebill1049 committed Feb 20, 2026
    Configuration menu
    Copy the full SHA
    85684f9 View commit details
    Browse the repository at this point in the history
Loading