chore(deps): bump react-i18next from 17.0.6 to 17.0.8

[dependabot]

Bumps react-i18next from 17.0.6 to 17.0.8.

Changelog

Sourced from react-i18next's changelog.

17.0.8

• fix(types): <Trans i18nKey={$ => ...}> now typechecks under enableSelector: 'strict'. The Trans component's conditional type was gated on _EnableSelector extends true | 'optimize', excluding 'strict' and falling back to the legacy string-key signature. Runtime was already correct (it calls keyFromSelector(i18nKey) whenever typeof i18nKey === 'function'); this is a type-only fix that widens the conditional to include 'strict'. Thanks @​Faithfinder (#1921)

17.0.7

• feat: useTranslation([nsA, nsB, ...]) now passes its full namespace list to getFixedT via the new scopeNs opt (requires i18next ≥ v26.0.10). This makes selector calls with a secondary-namespace prefix resolve correctly under default nsMode: t($ => $.nsB.foo) previously missed silently because the bound ns was the primary string only and i18next's selector rewrite needed an array. Resolution semantics are unchanged — plain t('key') lookups still stay isolated to the primary namespace by default; use nsMode: 'fallback' to opt into multi-ns fallback resolution as before. Fixes i18next#2429 for useTranslation-based callers.

Commits

• a46ad23 17.0.8
• f715031 update i18next dep
• a515d5b changelog: 17.0.8 entry for #1921
• d5ab7c8 fix(types): accept selector i18nKey on <Trans> under enableSelector: 'strict'...
• b91ba36 Add Locize advice section near the top of README
• 5e892a2 17.0.7
• c8f4c6b feat: useTranslation([nsA,nsB]) routes selector secondary-ns prefix via getFi...
• 084f9a6 Modernize locize.com URLs and refresh UTM tags
• 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 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)

[dependabot]

Labels

The following labels could not be found: javascript. Please create it before Dependabot can add it to a pull request.

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

[greptile-apps]

Greptile Summary

Routine Dependabot bump of react-i18next from 17.0.6 to 17.0.8. The two intermediate releases include a type-only fix for <Trans> under enableSelector: 'strict' and a useTranslation multi-namespace selector improvement that requires i18next >= 26.2.0.

• package.json: specifier updated from ^17.0.6 to ^17.0.8.
• pnpm-lock.yaml: resolved version, integrity hash, and peer-dep lower bound for i18next updated to >= 26.2.0; the project already pins i18next@26.2.0, so the constraint is satisfied.

Confidence Score: 5/5

Safe to merge — this is a two-patch bump containing a type-only fix and a minor multi-namespace feature; no runtime behaviour changes affect the main path.

Both 17.0.7 and 17.0.8 are non-breaking: 17.0.8 is a TypeScript-types-only change and 17.0.7 adds opt-in multi-namespace selector routing. The tightened peer dependency minimum (i18next >= 26.2.0) is already met by the project's locked i18next@26.2.0, so no compatibility gap exists.

No files require special attention.

Important Files Changed

Filename	Overview
package.json	Bumps react-i18next specifier from ^17.0.6 to ^17.0.8; no other changes.
pnpm-lock.yaml	Lock file updated to resolve react-i18next@17.0.8; peer dep minimum for i18next tightened to >= 26.2.0 (already satisfied by the project's i18next@26.2.0).

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["package.json\nreact-i18next ^17.0.8"] --> B["pnpm-lock.yaml\nreact-i18next@17.0.8"]
    B --> C["peer: i18next >= 26.2.0"]
    B --> D["peer: react >= 16.8.0"]
    E["project uses\ni18next@26.2.0"] -->|satisfies| C
    F["project uses\nreact@19.2.6"] -->|satisfies| D

Loading

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