chore(deps): bump react-i18next from 16.5.4 to 17.0.2 in /frontend

[dependabot]

Bumps react-i18next from 16.5.4 to 17.0.2.

Changelog

Sourced from react-i18next's changelog.

17.0.2

• fix(types): values prop on <Trans /> now only requires interpolation variables for the specific i18nKey, not all variables in the namespace 1913

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

... (truncated)

Commits

• 4d62f86 17.0.2
• 61fe80c fix(types): values prop on \<Trans /> now only requires interpolation vari...
• b58d5a5 l10n: add Swedish language support to examples (#1912)
• 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...
• 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)

Greptile Summary

This Dependabot PR bumps react-i18next from 16.5.4 to 17.0.2 in the frontend. The upgrade is straightforward for most of the codebase — no <Trans> components are used anywhere in frontend/src, so the breaking change in 17.0.0 (auto-generated key serialization for HTML nodes with interpolation) has no impact here.

However, there is one blocking issue: react-i18next 17.x requires i18next >= 26.0.1 as a peer dependency (bumped in 17.0.1), but the project still declares \"i18next\": \"^25.8.13\" and resolves to 25.8.13 in the lock file. This peer dependency conflict must be addressed — either by upgrading i18next to v26 in the same PR, or by reverting react-i18next to a 16.x release.

• react-i18next bumped from 16.5.4 → 17.0.2
• @babel/runtime bumped transitively from 7.28.6 → 7.29.2
• No <Trans> components found in the codebase — 17.0.0 breaking change does not apply
• i18next remains at 25.8.13, which violates the new >= 26.0.1 peer dependency requirement of react-i18next 17.x

Confidence Score: 4/5

Not safe to merge as-is — the i18next peer dependency must be upgraded to >= 26.0.1 alongside this bump.

There is one clear P1 issue: the installed i18next 25.8.13 does not satisfy the >= 26.0.1 peer dependency declared by react-i18next 17.x, which can lead to npm install conflicts and potential runtime failures. The fix is straightforward (upgrade i18next to v26), but it must be done before merging.

frontend/package.json — i18next version needs to be upgraded from ^25.8.13 to ^26.0.1

Important Files Changed

Filename	Overview
frontend/package.json	Bumps react-i18next to ^17.0.2, but the companion i18next peer dependency is still ^25.8.13 — below the new minimum of >= 26.0.1 required by 17.x.
frontend/package-lock.json	Lock file updated for react-i18next 17.0.2 and @babel/runtime 7.29.2; i18next remains locked at 25.8.13, confirming the peer dependency mismatch in package.json.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[react-i18next 17.0.2] -->|peerDep: i18next >= 26.0.1| B{i18next version?}
    B -->|Currently: 25.8.13 ❌| C[Peer dependency conflict\nnpm install warning/error\nPossible runtime failures]
    B -->|Required: >= 26.0.1 ✅| D[Compatible — safe to use]
    C --> E[Fix: upgrade i18next to ^26.0.1\nin package.json]
    E --> D

Loading

Comments Outside Diff (1)

1. frontend/package.json, line 57 (link)

   Unsatisfied peer dependency: i18next version too old

   react-i18next v17.0.1 bumped the minimum required peer dependency to i18next >= 26.0.1, but the project still declares "i18next": "^25.8.13" and package-lock.json resolves it to 25.8.13.

   This mismatch means:

   • npm install will emit a peer dependency conflict warning (or error with --legacy-peer-deps not set).
   • At runtime, react-i18next 17.x may call APIs introduced in i18next 26 that do not exist in 25.x, which can cause silent failures or exceptions.

   To resolve this, i18next should be upgraded alongside this bump:

   If upgrading i18next to v26 is not yet desired, this react-i18next bump should be held back to a 16.x release that still accepts i18next >= 25.x.

   Prompt To Fix With AI

   This is a comment left during a code review.
   Path: frontend/package.json
   Line: 57
   
   Comment:
   **Unsatisfied peer dependency: i18next version too old**
   
   `react-i18next` v17.0.1 bumped the minimum required peer dependency to `i18next >= 26.0.1`, but the project still declares `"i18next": "^25.8.13"` and `package-lock.json` resolves it to `25.8.13`.
   
   This mismatch means:
   - `npm install` will emit a peer dependency conflict warning (or error with `--legacy-peer-deps` not set).
   - At runtime, `react-i18next` 17.x may call APIs introduced in i18next 26 that do not exist in 25.x, which can cause silent failures or exceptions.
   
   To resolve this, `i18next` should be upgraded alongside this bump:
   
   If upgrading `i18next` to v26 is not yet desired, this `react-i18next` bump should be held back to a 16.x release that still accepts `i18next >= 25.x`.
   
   How can I resolve this? If you propose a fix, please make it concise.

Prompt To Fix All With AI

This is a comment left during a code review.
Path: frontend/package.json
Line: 57

Comment:
**Unsatisfied peer dependency: i18next version too old**

`react-i18next` v17.0.1 bumped the minimum required peer dependency to `i18next >= 26.0.1`, but the project still declares `"i18next": "^25.8.13"` and `package-lock.json` resolves it to `25.8.13`.

This mismatch means:
- `npm install` will emit a peer dependency conflict warning (or error with `--legacy-peer-deps` not set).
- At runtime, `react-i18next` 17.x may call APIs introduced in i18next 26 that do not exist in 25.x, which can cause silent failures or exceptions.

To resolve this, `i18next` should be upgraded alongside this bump:
```suggestion
    "i18next": "^26.0.1",
```
If upgrading `i18next` to v26 is not yet desired, this `react-i18next` bump should be held back to a 16.x release that still accepts `i18next >= 25.x`.

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "chore(deps): bump react-i18next from 16...." | Re-trigger Greptile}