From c83df091b1a5207375eaf23466bb5c62e4e1518e Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Thu, 1 Oct 2026 22:06:28 -0700
Subject: [PATCH] build(deps): bump react-i18next from 17.0.12 to 17.0.15
(#12970)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Bumps [react-i18next](https://github.com/i18next/react-i18next) from
17.0.12 to 17.0.15.
Changelog
Sourced from react-i18next's
changelog.
17.0.15
- fix(Trans): empty paired component tags now preserve a component's
single valid React-element child, whether supplied through a named
component map (
<wrap></wrap>), a component
array (<0></0>), or indexed JSX children
(<1></1>). This matches the existing behavior
for two or more children and self-closing tags. React represents one JSX
child as an element and multiple children as an array; the previous
array-only check silently rendered the one-child case empty.
Compatibility note: when that sole element contains an interpolation
object, the restored raw children can expose an existing React rendering
limitation as an error instead of silently rendering empty; the same
shape already errors with two children. Fixes #1932.
17.0.14
- fix: the
i18n object returned by
useTranslation was only refreshed when
i18n.language changed, so a resolvedLanguage
(or languages) change of its own kept handing components
the previous snapshot. That happens whenever the translations for the
current language arrive after the switch — i18next resolves to the
fallback until its store has them — and components reading
i18n.resolvedLanguage (language switchers, for example)
then stayed one switch behind. The cached wrapper is now keyed on all
three language fields, which are exactly the ones the surrounding
useMemo already depends on; wrapper identity still only
changes when the language state does, so the caching from #1885
is unaffected. Reported via next-i18next#2348.
17.0.13
- fix(types): the selector-form
keyPrefix overload of
useTranslation() is now available under
enableSelector: 'strict'. useTranslation was
gated on true | 'optimize' only, so under
'strict' it resolved to the legacy signature and the
selector overload disappeared entirely (keyPrefix: ($) =>
$.ns.foo failed with Type '($: any) => any' is not
assignable to type 'undefined'). Trans already
handled all three modes. Companion to the same fix for
getFixedT in i18next#2446.
Thanks @hovelopin (#1930).
Commits
7d38e09
17.0.15875b327
fix(Trans): preserve single-element children in empty slots5f8c5f9
17.0.146def81a
fix: refresh the returned i18n wrapper when resolvedLanguage
changesf37ea87
docs: "For AI assistants" paragraph in the READMEe0592ba
chore: keep dev-only and local files out of the npm packageaddf646
17.0.137c634ee
changelog v17.0.135ceefb0
fix(types): allow selector keyPrefix in useTranslation under
enableSelector '...aa7ba52
chore(examples): require activesupport >= 7.2.3.1 in the RN
Gemfiles- Additional commits viewable in compare
view
Signed-off-by: dependabot[bot]
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
---
pnpm-lock.yaml | 14 +++++++-------
ui/package.json | 2 +-
2 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
index 69e092c54ad..7398677807b 100644
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@@ -1197,8 +1197,8 @@ importers:
specifier: ^19.2.8
version: 19.2.8(react@19.2.8)
react-i18next:
- specifier: ^17.0.12
- version: 17.0.12(i18next@26.4.2(typescript@7.0.2))(react-dom@19.2.8(react@19.2.8))(react@19.2.8)(typescript@7.0.2)
+ specifier: ^17.0.15
+ version: 17.0.15(i18next@26.4.2(typescript@7.0.2))(react-dom@19.2.8(react@19.2.8))(react@19.2.8)(typescript@7.0.2)
react-markdown:
specifier: ^10.1.0
version: 10.1.0(@types/react@19.2.18)(react@19.2.8)
@@ -7965,8 +7965,8 @@ packages:
peerDependencies:
react: ^19.2.8
- react-i18next@17.0.12:
- resolution: {integrity: sha512-lFWPEGkxQ6RhusdUkysFBD58VHfSSzvHBzqMgN0SvfVpdQGfwtNkStTqdy08/sJd7s807qqutgx93fRpD0DJ3Q==}
+ react-i18next@17.0.15:
+ resolution: {integrity: sha512-7uYpx/oBkesLto7cOzOmfITlUBaXHCAcFahmgETMfWr8nbbWRRnVGvz8wsH/xpbNcyoH+NpCcnOQEqWPMO6/hw==}
peerDependencies:
i18next: '>= 26.2.0'
react: ^19.2.8
@@ -9435,7 +9435,7 @@ snapshots:
react: 19.2.8
react-dom: 19.2.8(react@19.2.8)
reselect: 5.2.0
- use-sync-external-store: 1.7.0(react@19.2.8)
+ use-sync-external-store: 1.6.0(react@19.2.8)
optionalDependencies:
'@types/react': 19.2.18
@@ -16081,13 +16081,13 @@ snapshots:
dependencies:
react: 19.2.8
- react-i18next@17.0.12(i18next@26.4.2(typescript@7.0.2))(react-dom@19.2.8(react@19.2.8))(react@19.2.8)(typescript@7.0.2):
+ react-i18next@17.0.15(i18next@26.4.2(typescript@7.0.2))(react-dom@19.2.8(react@19.2.8))(react@19.2.8)(typescript@7.0.2):
dependencies:
'@babel/runtime': 7.29.7
html-parse-stringify: 4.0.1
i18next: 26.4.2(typescript@7.0.2)
react: 19.2.8
- use-sync-external-store: 1.6.0(react@19.2.8)
+ use-sync-external-store: 1.7.0(react@19.2.8)
optionalDependencies:
react-dom: 19.2.8(react@19.2.8)
typescript: 7.0.2
diff --git a/ui/package.json b/ui/package.json
index 1930a00bbd2..5df3a92d6e0 100644
--- a/ui/package.json
+++ b/ui/package.json
@@ -65,7 +65,7 @@
"radix-ui": "^1.6.7",
"react": "^19.2.8",
"react-dom": "^19.2.8",
- "react-i18next": "^17.0.12",
+ "react-i18next": "^17.0.15",
"react-markdown": "^10.1.0",
"react-resizable-panels": "^4.12.3",
"react-router-dom": "^7.18.4",