A field-array fix survived eight days before its author reverted it
react-hook-form shipped a fix for stale field-array values on 9 May. On 17 May the maintainer pulled it back out and landed a regression test instead.
Incident: MAY 17, 2026react-hook-form/react-hook-formBy the desk
For eight days react-hook-form carried a fix that was supposed to make nested setValue calls reach every field array watching the name being written. It came back out on a Sunday night, and the commit that replaced it added no behaviour at all.
The fix landed on 9 May as part of pull request 13420, which claimed to close an issue opened in January about field values in useFieldArray failing to update after a setValue call.[2][4] Its whole mechanism was a new helper that walked a dotted field name outward and collected every registered ancestor that looked like an array root.[5] The loop rebuilt the prefix one segment at a time and pushed any prefix that was both a known name and immediately followed by a numeric index.[5]