chore(deps): bump the react group with 3 updates

[dependabot]

Bumps the react group with 3 updates: react-day-picker, react-email and react-hook-form.

Updates react-day-picker from 8.10.1 to 9.14.0

Release notes

Sourced from react-day-picker's releases.

v9.14.0

This release introduces a new resetOnSelect prop and adds support for the Hijri calendar.

Resetting Selections in Range Mode

When in range selection mode, use the new resetOnSelect prop to start a new range when a full range is already selected.

Hijri Calendar

To use the Hijri (Umm al-Qura) calendar, import DayPicker from react-day-picker/hijri:

import { DayPicker } from "react-day-picker/hijri";
export function HijriCalendar() {
return <DayPicker />;
}

Read more in the documentation and play with it in playground.

What's Changed

• feat: Add Hijri calendar support (Umm al-Qura) by @​ws-rush in gpbl/react-day-picker#2904
• feat: New resetOnSelect prop to reset date range when selecting date with completed range by @​rodgobbi in gpbl/react-day-picker#2906
• feat: add default lang prop to DayPicker root element by @​gpbl in gpbl/react-day-picker#2907

New Contributors

• @​ws-rush made their first contribution in gpbl/react-day-picker#2904

Full Changelog: gpbl/react-day-picker@v9.13.2...v9.14.0

v9.13.2

What's Changed

• fix(build): add correct type declaration for style.css export by @​NotNestor in gpbl/react-day-picker#2897
• fix(locale): correct Northern Sami (se) and Japanese Hiragana (ja-Hira) labels by @​gpbl in gpbl/react-day-picker#2898

New Contributors

• @​NotNestor made their first contribution in gpbl/react-day-picker#2897

Full Changelog: gpbl/react-day-picker@v9.13.1...v9.13.2

v9.13.1

Persian calendar improvements.

What's Changed

• feat: add narrow weekday format for Persian calendar by @​rezaaa in gpbl/react-day-picker#2895

New Contributors

• @​rezaaa made their first contribution in gpbl/react-day-picker#2895

... (truncated)

Commits

• a5b0c43 Prepare 9.14.0 package metadata
• 758f604 feat: add lang attribute to DayPicker root (#2907)
• 0893c96 feat: New resetOnSelect prop to reset date range when selecting date with com...
• 8e69eb1 feat: Add Hijri calendar support (Umm al-Qura) (#2904)
• 091ca6f chore: remove performance-tests project (#2902)
• 6df3193 chore: update workspace dependencies (#2901)
• 5208d3f chore: update workspace dependencies (#2900)
• 38e1b27 fix(locale): correct Northern Sami (se). and Japanese Hiragana (ja-Hira) labe...
• d68dc63 build: bump v9.13.2
• 12cf80b fix: add correct type declaration for style.css export (#2897)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for react-day-picker since your current version.

Updates react-email from 2.1.5 to 6.0.5

Release notes

Sourced from react-email's releases.

react-email@6.0.5

No release notes provided.

react-email@6.0.4

Patch Changes

• 96af3a7: Replace ora with picospinner for CLI and preview spinner output.
• 5cf57ae: unpin esbuild
• Updated dependencies [e0e896f]
  • @​react-email/render@​2.0.8

react-email@6.0.3

Patch Changes

• bb51e5e: fix missing react and react-dom peer dependencies

react-email@6.0.2

Patch Changes

• 63b6e71: Fix Markdown component crashing on CommonMark loose lists with paragraph continuations

react-email@6.0.1

Patch Changes

• 599b8c5: fix type issues in starter template and in react-email

react-email@6.0.0

Major Changes

• d0a7a52: Move all components and utilities into the react-email package

  All components (previously in @react-email/components or individual packages like @react-email/button) and rendering utilities (previously in @react-email/render) are now exported directly from react-email. This unifies the install and import experience into a single package.

  We're going to deprecate all packages except @react-email/render and @react-email/ui, and they will not be updated anymore.

  Breaking change

  Imports from @react-email/components, @react-email/render, or individual component packages (e.g. @react-email/button) are no longer the recommended path and they will all be deprecated with the exception of @react-email/render and @react-email/editor, and render will remain exported from react-email. Consumers should import everything from react-email.

  Why

  Having separate packages for components (@react-email/components), and the CLI (react-email) created unnecessary confusion, and a maintenance burden for us.

  How to migrate

  1. Remove @react-email/components:

     npm remove @react-email/components

... (truncated)

Changelog

Sourced from react-email's changelog.

6.0.5

6.0.4

Patch Changes

• 96af3a7: Replace ora with picospinner for CLI and preview spinner output.
• 5cf57ae: unpin esbuild
• Updated dependencies [e0e896f]
  • @​react-email/render@​2.0.8

6.0.3

Patch Changes

• bb51e5e: fix missing react and react-dom peer dependencies

6.0.2

Patch Changes

• 63b6e71: Fix Markdown component crashing on CommonMark loose lists with paragraph continuations

6.0.1

Patch Changes

• 599b8c5: fix type issues in starter template and in react-email

6.0.0

Major Changes

• d0a7a52: Move all components and utilities into the react-email package

  All components (previously in @react-email/components or individual packages like @react-email/button) and rendering utilities (previously in @react-email/render) are now exported directly from react-email. This unifies the install and import experience into a single package.

  We're going to deprecate all packages except @react-email/render and @react-email/ui, and they will not be updated anymore.

  Breaking change

  Imports from @react-email/components, @react-email/render, or individual component packages (e.g. @react-email/button) are no longer the recommended path and they will all be deprecated with the exception of @react-email/render and @react-email/editor, and render will remain exported from react-email. Consumers should import everything from react-email.

  Why

  Having separate packages for components (@react-email/components), and the CLI (react-email) created unnecessary confusion, and a maintenance burden for us.

  How to migrate

  1. Remove @react-email/components:

... (truncated)

Commits

• d03a14f chore(root): version packages (#3452)
• 961d1d2 chore(root): version packages (#3445)
• 96af3a7 feat(react-email): replace ora with picospinner (#3442)
• 5cf57ae chore(react-email): unpin esbuild (#3441)
• ec50c6d chore(root): version packages (#3436)
• bb51e5e fix(react-email): missing react peer dependencies (#3439)
• 32e4d0b chore(root): version packages (#3429)
• 63b6e71 fix(markdown): crash on loose lists with paragraph continuation (#3432) (#3433)
• ad69b8f chore(root): version packages (#3427)
• 599b8c5 fix: missing types in tsconfig, and type errors in starter template (#3423)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for react-email since your current version.

Updates react-hook-form from 7.61.1 to 7.75.0

Release notes

Sourced from react-hook-form's releases.

Version 7.75.0

🦧 feat: improve get dirty fields prune empty fields (#13363)

+ dirtyFields: { test: [{ data: false }] }
- dirtyFields: {} // removed the empty node with false value

🎹 typescript 6.0 (#13330) 🌡️ chore: minor improvement on setValue & reset (#13366) 🐞 fix #13403: include setValues in FormProvider context value (#13404) 🐞 fix: recompute isDirty after re-registering a previously unregistered field (#13399) 🐞 fix: preserve watch updates on field array unmount fixes #13375 (#13385) 🐞 fix: prevent useWatch re-render when unrelated field validation is … (#13398)

thanks to @​dfedoryshchev, @​cyky & @​gkarabelos

Version 7.74.0

🪇 feat: setValues (#13201)

setValues((data) => {
  return {
    ...data,
    name: 'test'
  }
})
setValues(formValues);

🐞 fix: preserve previous field value when useController name changes (#13395) 🐞 fix: handle null parent when unregistering nested field (#13396) 🐞 fix: treat NaN as empty when valueAsNumber is true in validateField (#13388) 🪢 fix build to exclude test files (#13387)

thanks to @​Yihao-G & @​mixelburg

Version 7.73.1

⚡perf: memoize submit (#13378) 🚉 perf: improve deepEqual performance (#13362) 👀 perf: skip re-render in setValue when value is unchanged (#13352) ✂️ remove unneeded flag check for shouldDirty 🚨 fix: safely access field._f during register (#13365) 🧹 close #13298: improve fieldState errors when resolver uses dot-notation string keys (#13350) 🐞 fix #13178: update state correctly in watch callback with Controller, trigger, and reset (#13180) 🐞 fix #13331: skip field array validation when mode is onBlur (#13333) 🐞 fix #13334 sDirty remains false after deletion an item with shouldDirty: true (#13357) 🐞 fix: handle nested field when parent defaultValue is null (#13348)

... (truncated)

Changelog

Sourced from react-hook-form's changelog.

[7.75.0] - 2026-05-02

Added

• Improve getDirtyFields to prune empty fields
• TypeScript 6.0 support

Fixed

• Include setValues in FormProvider context value
• Preserve watch updates on field array unmount
• Prevent useWatch re-render when unrelated field validation occurs
• Recompute isDirty after re-registering a previously unregistered field

[7.74.0] - 2026-04-26

Added

• setValues API

Fixed

• Preserve previous field value when useController name changes
• Handle null parent when unregistering nested field
• Treat NaN as empty when valueAsNumber is true in validateField

[7.73.1] - 2026-04-21

Fixed

• Reverted setValues that was accidentally included in patch; fix build to exclude test files

[7.73.0] - 2026-04-18

Added

• Improve subscribe API performance

Performance

• Memoize submit handler
• Improve deepEqual performance

Fixed

• Safely access field._f during register
• Improve fieldState errors when resolver uses dot-notation string keys
• Update state correctly in watch callback with Controller, trigger, and reset
• Skip field array validation when mode is onBlur
• isDirty remains false after deleting an item with shouldDirty: true

... (truncated)

Commits

• 24bde23 7.75.0
• aa6f795 🐞 fix #13403: include setValues in FormProvider context value (#13404)
• c2b22f9 🥊 all ts-ignores removed
• 3165a52 🧸 fix more @​ts-ignores
• 7c51590 🧸 fix more @​ts-ignores
• b16b4fa 🎹 typescript 6.0 (#13330)
• 4bace71 🐞 fix: preserve watch updates on field array unmount fixes #13375 (#13385)
• 2adb9c0 🐞 fix: prevent useWatch re-render when unrelated field validation is … (#13398)
• f5a234d 🦧 feat: improve get dirty fields prune empty fields (#13363)
• def8fd5 🐞 fix: recompute isDirty after re-registering a previously unregistered field...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Assignees

The following users could not be added as assignees: your-github-username. Either the username does not exist or it does not have the correct permissions to be added as an assignee.

Labels

The following labels could not be found: automated, dependencies. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.