chore(deps): bump react-i18next from 16.5.8 to 17.0.1

[dependabot]

Bumps react-i18next from 16.5.8 to 17.0.1.

Changelog

Sourced from react-i18next's changelog.

17.0.1

• chore: bump minimum i18next peer dependency to >= 26.0.1 (forgot to do it in last version)
• fix: migrate test setup from removed legacy interpolation.format to i18n.services.formatter.add() (i18next v26)

17.0.0

Potentially breaking changes

• fix: transKeepBasicHtmlNodesFor now correctly preserves HTML tag names when children contain interpolations or mixed content 230
  • Previously, <strong>{{name}}</strong> was incorrectly serialized as <1>{{name}}</1> — the tag name was only preserved for plain string children
  • This bug existed since the feature was introduced and affects auto-generated keys (when no explicit i18nKey is provided)
  • If you rely on auto-generated Trans keys containing indexed tags for kept HTML elements with interpolation children, you will need to update your translation files

Other changes

• updated dev dependencies (vitest, rollup plugins, happy-dom, typescript, etc.)

16.6.6

• fix(peer-deps): bump i18next peer dependency to >= 25.10.9 to match required type exports (ConstrainTarget, ApplyTarget, GetSource) used by TransSelector 1911

16.6.5

• fix(types): selector keyPrefix overload in useTranslation no longer matches when keyPrefix is absent, fixing defaultNS: false with explicit ns option 2412

16.6.4

• allow TypeScript 6 as peer dependency 1910

16.6.3

• fix(types): merge TransSelector overloads into a single signature so typeof Trans remains extendable 1909

16.6.2

• feat(types): useTranslation now accepts selector functions as keyPrefix with full type-safe key narrowing when enableSelector is enabled 2367

16.6.1

• feat(types): i18nKey of <Trans i18nKey={sk} /> to accept a SelectorKey 2364

16.6.0

• warn when t is called before ready with useSuspense: false 1896
• type-safe values prop on <Trans /> component — interpolation variables are now inferred from the translation string when custom types are configured 1772

Commits

• 2321496 17.0.1
• 7e656b5 chore: bump minimum i18next peer dependency
• dfc350b upate github actions
• 7fe2620 17.0.0
• f4ada4c fix: transKeepBasicHtmlNodesFor now correctly preserves HTML tag names when...
• eb02c63 16.6.6
• 76f98cd fix(peer-deps): bump i18next peer dependency to >= 25.10.9 to match require...
• 9f830e1 16.6.5
• 9f0005f fix(types): selector keyPrefix overload in useTranslation no longer matches...
• f820b80 16.6.4
• 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

AI Analysis

Technical Summary:

This pull request upgrades the react-i18next dependency from version 16.5.8 to 17.0.1. The update includes multiple minor and major changes in the library along with some potentially breaking changes primarily due to internal API and behavior adjustments.

---

Technical Requirements and Constraints:

• The upgrade requires the minimum peer dependency of i18next to be bumped to >= 26.0.1 (previously >= 25.10.9), necessitating an update to at least this version of i18next in the project.
• The removal of legacy interpolation.format API requires migrating to the new i18n.services.formatter.add() method for formatting interpolations.
• TypeScript support has been improved and refined, including better type safety for useTranslation hooks and the <Trans /> component.
• Translations relying on auto-generated keys with HTML tags and interpolations must be

---

This summary was automatically generated by AI to help with triage and may not be 100% accurate.

[dependabot]

Superseded by #18.