Skip to content

[Snyk] Upgrade react-hook-form from 7.68.0 to 7.70.0#331

Open
chirag127 wants to merge 1 commit into
mainfrom
snyk-upgrade-ee97062043d2292c851bf6721a5dc964
Open

[Snyk] Upgrade react-hook-form from 7.68.0 to 7.70.0#331
chirag127 wants to merge 1 commit into
mainfrom
snyk-upgrade-ee97062043d2292c851bf6721a5dc964

Conversation

@chirag127
Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to upgrade react-hook-form from 7.68.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 2 versions 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

  • 7.68.0 - 2025-12-03

    🎧 feat: <FormStateSubscribe /> component (#13142)

    import { useForm, FormStateSubscribe } from 'react-hook-form';

    const App = () => {
    const { register, control } = useForm();

    return (
    <div>
    <form>
    <input {...register('foo')} />
    <input {...register('bar')} />
    </form>
    {/* re-render only when formState of foo changes */}
    <FormStateSubscribe
    control={control}
    name={"foo"}
    render={({errors}) => <span>{errors.foo?.message}</span>}
    />
    </div>
    );
    };

    🐞 fix: clear validation errors synchronously in reset() to fix Next.js 16 Server Actions issue (#13139)
    Revert "✨ fix(types): allow undefined value with async defaultValues in Contr…" (#13171)

    thanks to @ xiangnuans, @ abnud11, @ ntatoud & @ ap0nia

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:

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

See this package in npm:
react-hook-form

See this project in Snyk:
https://app.snyk.io/org/chirag127/project/26942488-82ce-4394-b219-aef662d2386d?utm_source=github&utm_medium=referral&page=upgrade-pr
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jan 26, 2026

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

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

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @chirag127, I'm Gemini Code Assist1! 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 updates the react-hook-form library to its latest stable version, 7.70.0. This upgrade is crucial for maintaining the application's security posture and stability, as it includes important bug fixes, type enhancements, and addresses several security vulnerabilities, including a critical Remote Code Execution (RCE) vulnerability. By integrating these updates, the project benefits from improved form management capabilities and a more secure dependency landscape.

Highlights

  • Dependency Upgrade: Upgraded the react-hook-form library from version 7.68.0 to 7.70.0.
  • Security Fixes: Incorporated critical security patches, including a fix for CVE-2025-55182, a Critical RCE (Remote Code Execution) vulnerability, introduced in version 7.69.0.
  • Bug Fixes and Improvements: Included various bug fixes and type improvements from versions 7.69.0 and 7.70.0, enhancing the stability and correctness of form handling.
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
Copy link
Copy Markdown

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 package.json in the
repository root.
- 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'

- This indicates the workflow is running npm install in a directory that does not contain
package.json (e.g., the file is missing, named differently, or located in a subdirectory), causing
the step to exit with code 254.

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_12_46_929Z-debug-0.log
137:  ##[error]Process completed with exit code 254.
138:  Post job cleanup.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request, automatically generated by Snyk, upgrades the react-hook-form dependency from version 7.68.0 to 7.70.0. This is a beneficial and recommended update. The changes are confined to package.json and package-lock.json and correctly reflect the version bump. According to the release notes, this upgrade includes important bug fixes and security patches for several CVEs, one of which is a critical RCE vulnerability. Merging this PR is highly recommended to improve the security and stability of the application.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants