chore(deps): bump the production group in /web with 4 updates

[dependabot]

Bumps the production group in /web with 4 updates: @fontsource-variable/geist-mono, @fontsource-variable/inter, react-hook-form and react-i18next.

Updates @fontsource-variable/geist-mono from 5.2.8 to 5.3.0

Commits

• See full diff in compare view

Updates @fontsource-variable/inter from 5.2.8 to 5.3.0

Commits

• See full diff in compare view

Updates react-hook-form from 7.81.0 to 7.82.0

Release notes

Sourced from react-hook-form's releases.

Version 7.82.0

🚀 feat: add opt-in delayError option for setValue (#13337)

setValue("firstName", "Bill", {
  delayError: 500, // delay validation error updates by 500ms
  shouldValidate: true
});

⚡ perf: improve getDirtyFields performance (#13590)

• Improved dirty field calculation, especially for larger forms and deeply nested values.

🐞 fix: expose resetDefaultValues through form context (#13598)

const { resetDefaultValues } = useFormContext();
resetDefaultValues();

🐞 fix: setValue with shouldDirty now correctly updates dirty state when the form is disabled (#13594) 🐞 fix: preserve dirtyFields boolean values for registered array fields (#13586) 🐞 fix: restore FieldArray component export (#13596) 🧪 test: migrate test suite to Playwright and improve delayError test reliability (#13589)

thanks to @​candymask0712, @​wanxiankai, @​a-y-ibrahim, @​ankit1324 & @​abnud11

Changelog

Sourced from react-hook-form's changelog.

[7.82.0] - 2026-07-18

Added

• Opt-in delayError option for setValue to delay validation error updates

Fixed

• Expose resetDefaultValues through form context
• setValue with shouldDirty not updating dirty state correctly when the form is disabled
• Preserve dirtyFields boolean values for registered array fields
• Restore FieldArray component export

Performance

• Improve getDirtyFields performance, especially for larger forms and deeply nested values

Commits

• 553d290 7.82.0
• 2791e4f 🐞 fix: prevent stale _setValid() calls from overwriting isValid/isValidating ...
• 521adfc 🤦🏻‍♂️ fix: expose resetDefaultValues through form context (#13598)
• 2f7c1c5 🤧 fix FieldArray component export (#13596)
• 9378288 🐞 fix #13592 setValue with shouldDirty not marking dirty state when form is d...
• 65599cc 🚗 perf: improve get dirty fields (#13590)
• 142f299 🖲️ chore: upgrade pnpm to v11 (#13587)
• 673aae4 🤖 build(deps-dev): bump vite from 5.4.11 to 6.4.3 in /app (#13534)
• 11bd6df 🥗 migrate to playwright & fix delay error feature (#13589)
• 95da27a ⏳ feat: add opt-in delayError option for setValue (#13337)
• Additional commits viewable in compare view

Updates react-i18next from 17.0.9 to 17.0.10

Changelog

Sourced from react-i18next's changelog.

17.0.10

• fix(warnings): the useTranslation and Trans "You will need to pass in an i18next instance" warnings now match the useSSR wording, mentioning the props/context alternatives and the most common unexplained cause at scale: duplicate react-i18next copies in monorepo setups. The Trans variant also referenced the internal i18nextReactModule name; it now points to the public initReactI18next API.
• feat(warnings): development-only warning (SUSPENDED_WHILE_LOADING, logged once) right before useTranslation suspends while translations are loading. With the default useSuspense: true and no <Suspense> boundary this previously surfaced as a blank screen or a cryptic React error; the warning now names both fixes (add a <Suspense> boundary or set react.useSuspense: false). No-op in production builds; the process.env.NODE_ENV check is wrapped so runtimes without a process global (raw ESM in the browser, some edge runtimes) stay silent instead of throwing.
• ci: weekly workflow typechecking the test suite against @types/react@next / @types/react-dom@next, so the next React major's type changes (like the React 18 TFunctionResult/children wave) surface before user reports.

Commits

• 3b71c27 17.0.10
• 57c3500 build
• c62476f chore: sync package-lock with i18next ^26.2.0 devDependency bump
• 0126bd1 improve instance warnings (monorepo hint) + dev-only suspense warning + weekl...
• See full diff 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]

Labels

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

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

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.