[Snyk] Upgrade react-hook-form from 7.69.0 to 7.70.0

[chirag127]

Snyk has created this PR to upgrade react-hook-form from 7.69.0 to 7.70.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 1 version ahead of your current version.

• The recommended version was released 22 days ago.

Release notes

Package name: react-hook-form

• 7.70.0 - 2026-01-04
  

  ✅ watch type improvement (#13228)
  🐞 fix: prevent field array ghost elements with keepDirtyValues (#13188)
  🐞 fix: improve invalid date handling in deepEqual and validation (#13230)
  🐞 fix(types): handle branded types correctly in DeepPartial (#13222)
  🐞 fix native validation focus issue (#13220)
  🐞 change spread operator to set name with depricated names prop, then override with new name prop is supplied (#13214)
  🐞 fix: prevent duplicate subscription trigger in setValue (#13206) (#13209)
  👌 chore: fix lib type check include tests (#13229)

  thanks to @ EdwardEB, @ constantly-dev & @ a28689604

• 7.69.0 - 2025-12-20
  

  📏 feat: align API with useWatch (#13192)
  🤦🏻‍♂️ chore: update @ deprecated names prop on (#13198)
  🏥 chore: safely call function methods on elements (#13190)
  🪖 chore: cve-2025-67779 (#13196)
  🪖 chore: cve-2025-55184 & cve-2025-55183 (#13194)
  🪖 chore: CVE-2025-55182 Critical RCE vulnerabilty (#13175)
  🔬 test: add regression tests for #12837 and #13136 (#13187)
  🐞 fix(reset): preserve isValid state when keepIsValid option is used (#13173)
  🐞 fix: ensure each createFormControl.subscribe subscription listens only to the changes it subscribes to (#12968)
  🐞 fix(validation): batch isValidating state updates with validation result (#13181)
  🐞 fix(createFormControl): resolve race condition between setError and setFocus (#13138) (#13169)
  🧿 fix control prop type (#13189)
  🔔 chore: clean cloneObject logic (#13179)

  thanks to @ PierreCrb, @ a28689604, @ AnuragM7666, @ ap0nia, @ dusan233 & @ hlongc

from react-hook-form GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @chirag127, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request automates the process of keeping project dependencies current by upgrading the react-hook-form library to its latest patch version, 7.70.0. This update brings a collection of minor enhancements and critical bug fixes, ensuring the application benefits from improved stability, better type safety, and resolution of various form-related issues without introducing breaking changes.

Highlights

• Dependency Upgrade: Upgraded the react-hook-form library from version 7.69.0 to 7.70.0.
• Bug Fixes: Incorporates several bug fixes, including issues with field array ghost elements, invalid date handling in validation, native validation focus, and preventing duplicate subscription triggers in setValue.
• Type Improvements: Includes type improvements for the watch function and correct handling of branded types in DeepPartial.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[qodo-code-review]

CI Feedback 🧐

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: build

Failed stage: Install dependencies [❌]

Failed test name: ""

Failure summary: The action failed during the npm install step because npm could not find/read package.json at /home/runner/work/WebDev-Odyssey-Full-Stack-Bootcamp-Showcase-Portfolio/WebDev-Odyssey-Full-Stack-Bootcamp-Showcase-Portfolio/package.json (ENOENT: no such file or directory). This indicates the workflow is running in a directory that does not contain a Node project (missing package.json), or the repository checkout/path/working-directory is misconfigured.

Relevant error logs: 1: ##[group]Runner Image Provisioner 2: Hosted Compute Agent ... 114: node-version: 20 115: always-auth: false 116: check-latest: false 117: token: *** 118: ##[endgroup] 119: Found in cache @ /opt/hostedtoolcache/node/20.20.0/x64 120: ##[group]Environment details 121: node: v20.20.0 122: npm: 10.8.2 123: yarn: 1.22.22 124: ##[endgroup] 125: ##[group]Run npm install 126: �[36;1mnpm install�[0m 127: shell: /usr/bin/bash -e {0} 128: ##[endgroup] 129: npm error code ENOENT 130: npm error syscall open 131: npm error path /home/runner/work/WebDev-Odyssey-Full-Stack-Bootcamp-Showcase-Portfolio/WebDev-Odyssey-Full-Stack-Bootcamp-Showcase-Portfolio/package.json 132: npm error errno -2 133: npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '/home/runner/work/WebDev-Odyssey-Full-Stack-Bootcamp-Showcase-Portfolio/WebDev-Odyssey-Full-Stack-Bootcamp-Showcase-Portfolio/package.json' 134: npm error enoent This is related to npm not being able to find a file. 135: npm error enoent 136: npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2026-01-26T05_31_15_195Z-debug-0.log 137: ##[error]Process completed with exit code 254. 138: Post job cleanup.

[gemini-code-assist]

Code Review

This pull request is an automated dependency upgrade for react-hook-form from version 7.69.0 to 7.70.0, initiated by Snyk. This is a minor version bump that includes various bug fixes and type improvements, as detailed in the release notes. The changes appear to be non-breaking. The modifications to package.json and package-lock.json are correct for this upgrade. I recommend merging this PR after ensuring all continuous integration checks pass successfully.