[Snyk] Upgrade react-hook-form from 7.67.0 to 7.68.0

[chirag127]

Snyk has created this PR to upgrade react-hook-form from 7.67.0 to 7.68.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 25 days ago.

Release notes

Package name: react-hook-form

• 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

• 7.67.0 - 2025-11-28
  

  🎯 feat: add exact to useController props (#13154)

  useForm({
  defaultValues: {
  user: {
  name: ''
  }
  }
  })

  <Controller control={control} name="user" exact={false} /> // subscribe to all user object

  ✨ fix(types): allow undefined value with async defaultValues in Controller (#13160)
  🐞 fix(types): correct PathValueImpl type inference (#13150)

  thanks to @ ap0nia, @ Fasping & @ joseph0926

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

[continue]

Learn more

---

All Green is an AI agent that automatically:

✅ Addresses code review comments

✅ Fixes failing CI checks

✅ Resolves merge conflicts

---

Unsubscribe from All Green comments

[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.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch snyk-upgrade-549db882378955c9af45aaa9d0e4377c

---

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 upgrade of the react-hook-form dependency from version 7.67.0 to 7.68.0. This minor version bump brings a new component for fine-grained form state subscriptions and resolves a critical bug related to validation error clearing when using Next.js 16 Server Actions, ensuring better form management and compatibility.

Highlights

• react-hook-form Upgrade: The react-hook-form library has been upgraded from version 7.67.0 to 7.68.0.
• New FormStateSubscribe Component: Version 7.68.0 introduces a new <FormStateSubscribe /> component, enabling more granular subscriptions to form state changes for optimized re-renders.
• Validation Error Fix: A bug fix is included to synchronously clear validation errors in reset(), addressing an issue specifically with Next.js 16 Server Actions.

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: Lint [❌]

Failed test name: ""

Failure summary: The action failed during the npm run lint step because the project does not define a lint script in package.json. - Error: npm error Missing script: "lint" (step Run npm run lint) - The command exited with code 1, causing the GitHub Action to fail.

Relevant error logs: 1: ##[group]Runner Image Provisioner 2: Hosted Compute Agent ... 126: shell: /usr/bin/bash -e {0} 127: ##[endgroup] 128: added 124 packages, and audited 125 packages in 3s 129: 21 packages are looking for funding 130: run `npm fund` for details 131: 5 vulnerabilities (1 low, 4 high) 132: To address issues that do not require attention, run: 133: npm audit fix 134: To address all issues (including breaking changes), run: 135: npm audit fix --force 136: Run `npm audit` for details. 137: ##[group]Run npm run lint 138: �[36;1mnpm run lint�[0m 139: shell: /usr/bin/bash -e {0} 140: ##[endgroup] 141: npm error Missing script: "lint" 142: npm error 143: npm error Did you mean this? 144: npm error npm link # Symlink a package folder 145: npm error 146: npm error To see a list of scripts, run: 147: npm error npm run 148: npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2025-12-29T02_30_19_447Z-debug-0.log 149: ##[error]Process completed with exit code 1. 150: Post job cleanup.

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, upgrades react-hook-form from version 7.67.0 to 7.68.0. The changes are confined to package.json and package-lock.json to reflect this dependency update. My review focuses on dependency management best practices. I've noticed that the updated dependency in package.json uses a caret (^) version range. To improve build reproducibility and prevent unexpected issues from transitive dependency updates, I recommend pinning dependencies to their exact versions. I've left a specific suggestion to address this.

[gemini-code-assist]

To ensure more predictable and stable builds, it's a good practice to pin application dependencies to an exact version. Using a caret (^) can automatically pull in newer minor versions, which might introduce unexpected changes or bugs. I suggest removing the caret to pin react-hook-form to the exact version 7.68.0.

Suggested change

	"react-hook-form": "^7.68.0",
	"react-hook-form": "7.68.0",