From 057a6a07d8f826ddcc4b6700de3ac2b918838ecf Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Wed, 21 Oct 2026 13:55:11 +0000
Subject: [PATCH] chore(deps): Bump i18next from 26.4.7 to 26.5.2 (#2256)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

[//]: # (dependabot-start)
⚠️  **Dependabot is rebasing this PR** ⚠️

Rebasing might not happen immediately, so don't worry if this takes some
time.

Note: if you make any changes to this PR yourself, they will take
precedence over the rebase.

---

[//]: # (dependabot-end)

Bumps [i18next](https://github.com/i18next/i18next) from 26.4.7 to
26.5.2.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/i18next/i18next/releases">i18next's
releases</a>.</em></p>
<blockquote>
<h2>v26.5.2</h2>
<ul>
<li>fix(types): on TypeScript 7, a <code>t()</code> call with a missing,
misspelled or wrongly typed option now reports that option again
(<code>Property 'album' is missing</code>, <code>Type 'string' is not
assignable to type 'number'</code>), as TypeScript 5 and 6 do.
TypeScript 7 elaborated the error against the default-value signature
instead and ended in <code>'{ count: 3; albm: &quot;Summer&quot;; }' is
not assignable to type 'string'</code>: on a failed call TypeScript
explains the last of the equally matching signatures, and TypeScript 7
sorts the 3-element <code>[key, defaultValue, options?]</code> last. It
is now written as two signatures, <code>[key, defaultValue]</code> and
<code>[key, defaultValue, options]</code>. This affects the default key
checks with i18next <code>{{name}}</code> messages as well as
<code>parseInterpolation: 'icu'</code> and <code>'mf2'</code>. Which
calls compile, their return types and the error positions are unchanged
on TypeScript 5.9, 6 and 7.</li>
</ul>
<h2>v26.5.1</h2>
<ul>
<li>perf(types): type-checking <code>t()</code> calls against a large
namespace is no longer quadratic in the number of keys. TypeScript does
not cache <code>keyof</code> of an object type, and the types rebuilt
the union of all keys of a namespace once per key while building the key
union, and again in every <code>t()</code> call to look up the return
type. Both now use a cached key union, and a literal key is looked up
directly instead of being intersected with every key. With 5,000 keys in
one namespace and one call per key, the check time went from 14.8s to
1.1s (TypeScript 6); with 1,000 keys from 0.75s to 0.27s. Keys, return
types and errors are unchanged.</li>
<li>perf(types): the selector API (<code>enableSelector: true</code> /
<code>'strict'</code>) with <code>context</code> is no longer quadratic
in the size of an object. To decide which keys a context keeps, the
types scanned all keys of the object once for every key, also when
TypeScript checks the selector with <code>context</code> widened to
<code>string</code>. With 1,000 keys plus one context variant each, a
namespace took 18.7s and failed with &quot;Type instantiation is
excessively deep and possibly infinite&quot; (TS2589); 2,500 and more
ran out of memory. The context variants of an object are now collected
once, in one pass over its keys: 1,000 keys check in 0.69s, 5,000 in
3.1s. Long keys (whole sentences with <code>keySeparator: false</code>)
work as before. Selected values and errors are unchanged.</li>
</ul>
<h2>v26.5.0</h2>
<ul>
<li>feat(types): <code>parseInterpolation: 'icu'</code> and
<code>parseInterpolation: 'mf2'</code> type <code>t()</code> options
from the message's ICU MessageFormat arguments (i18next-icu) or
MessageFormat 2 variables (i18next-mf2), so ICU and MF2 users no longer
need <code>parseInterpolation: false</code> and lose argument checking.
Missing, misspelled and wrongly typed arguments fail, and so does
leaving out the options for a message with arguments
(<code>t('greeting')</code>); that error names the missing arguments.
Opt-in, default <code>true</code> is unchanged.
<ul>
<li>ICU: <code>{name}</code> takes <code>string | number</code>,
<code>{n, number}</code>, <code>plural</code> and
<code>selectordinal</code> take <code>number</code>, <code>{d,
date}</code> and <code>{t, time}</code> take <code>Date</code>,
<code>select</code> takes its case keys or any string (for
<code>other</code>), and arguments nested in cases are required too.
<code>#</code> and tags are not arguments, apostrophe quoting is read
like intl-messageformat does.</li>
<li>MF2: <code>{$name}</code> takes <code>string | number</code>, a
variable annotated with <code>:number</code>, <code>:integer</code>,
<code>:currency</code>, <code>:percent</code> or <code>:unit</code>
(inline or through <code>.input</code> / <code>.local</code>) takes
<code>number</code>, <code>:datetime</code>, <code>:date</code> and
<code>:time</code> take <code>Date</code>, <code>:string</code> takes
<code>string</code>, option and markup variables
(<code>minimumFractionDigits=$digits</code>, <code>{#link
href=$url}</code>) are required too, <code>.local</code> variables are
not arguments, and <code>|quoted literals|</code> and <code>\{</code>
escapes are skipped.</li>
<li><code>interpolationFormatTypeMap</code> overrides a type by ICU
format or MF2 function name, e.g. <code>date: Date | number</code> or a
custom <code>uppercase: string</code>.</li>
<li>Applies to <code>t()</code>, <code>getFixedT()</code>,
<code>i18n.t</code>, key prefixes, namespaces, the selector API and
react-i18next's <code>Trans</code> <code>values</code>. Messages need
literal types, as the resources file from i18next-cli's
<code>types</code> command has them.</li>
<li>Type-check cost with 1,000 messages and one call each: 1.35s instead
of 0.86s with <code>false</code> (TypeScript 6), 0.5s instead of 0.26s
with TypeScript 7. Messages that no call uses cost nothing.</li>
</ul>
</li>
<li>fix(types): with the default (non-strict) key checks, an options
object with a missing or misspelled interpolation variable now reports
the missing variable (<code>Property 'name' is missing</code>) instead
of <code>'{ nmae: string }' is not assignable to type 'string'</code>
from the default-value overload.</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/i18next/i18next/blob/master/CHANGELOG.md">i18next's
changelog</a>.</em></p>
<blockquote>
<h2>26.5.2</h2>
<ul>
<li>fix(types): on TypeScript 7, a <code>t()</code> call with a missing,
misspelled or wrongly typed option now reports that option again
(<code>Property 'album' is missing</code>, <code>Type 'string' is not
assignable to type 'number'</code>), as TypeScript 5 and 6 do.
TypeScript 7 elaborated the error against the default-value signature
instead and ended in <code>'{ count: 3; albm: &quot;Summer&quot;; }' is
not assignable to type 'string'</code>: on a failed call TypeScript
explains the last of the equally matching signatures, and TypeScript 7
sorts the 3-element <code>[key, defaultValue, options?]</code> last. It
is now written as two signatures, <code>[key, defaultValue]</code> and
<code>[key, defaultValue, options]</code>. This affects the default key
checks with i18next <code>{{name}}</code> messages as well as
<code>parseInterpolation: 'icu'</code> and <code>'mf2'</code>. Which
calls compile, their return types and the error positions are unchanged
on TypeScript 5.9, 6 and 7.</li>
</ul>
<h2>26.5.1</h2>
<ul>
<li>perf(types): type-checking <code>t()</code> calls against a large
namespace is no longer quadratic in the number of keys. TypeScript does
not cache <code>keyof</code> of an object type, and the types rebuilt
the union of all keys of a namespace once per key while building the key
union, and again in every <code>t()</code> call to look up the return
type. Both now use a cached key union, and a literal key is looked up
directly instead of being intersected with every key. With 5,000 keys in
one namespace and one call per key, the check time went from 14.8s to
1.1s (TypeScript 6); with 1,000 keys from 0.75s to 0.27s. Keys, return
types and errors are unchanged.</li>
<li>perf(types): the selector API (<code>enableSelector: true</code> /
<code>'strict'</code>) with <code>context</code> is no longer quadratic
in the size of an object. To decide which keys a context keeps, the
types scanned all keys of the object once for every key, also when
TypeScript checks the selector with <code>context</code> widened to
<code>string</code>. With 1,000 keys plus one context variant each, a
namespace took 18.7s and failed with &quot;Type instantiation is
excessively deep and possibly infinite&quot; (TS2589); 2,500 and more
ran out of memory. The context variants of an object are now collected
once, in one pass over its keys: 1,000 keys check in 0.69s, 5,000 in
3.1s. Long keys (whole sentences with <code>keySeparator: false</code>)
work as before. Selected values and errors are unchanged.</li>
</ul>
<h2>26.5.0</h2>
<ul>
<li>feat(types): <code>parseInterpolation: 'icu'</code> and
<code>parseInterpolation: 'mf2'</code> type <code>t()</code> options
from the message's ICU MessageFormat arguments (i18next-icu) or
MessageFormat 2 variables (i18next-mf2), so ICU and MF2 users no longer
need <code>parseInterpolation: false</code> and lose argument checking.
Missing, misspelled and wrongly typed arguments fail, and so does
leaving out the options for a message with arguments
(<code>t('greeting')</code>); that error names the missing arguments.
Opt-in, default <code>true</code> is unchanged.
<ul>
<li>ICU: <code>{name}</code> takes <code>string | number</code>,
<code>{n, number}</code>, <code>plural</code> and
<code>selectordinal</code> take <code>number</code>, <code>{d,
date}</code> and <code>{t, time}</code> take <code>Date</code>,
<code>select</code> takes its case keys or any string (for
<code>other</code>), and arguments nested in cases are required too.
<code>#</code> and tags are not arguments, apostrophe quoting is read
like intl-messageformat does.</li>
<li>MF2: <code>{$name}</code> takes <code>string | number</code>, a
variable annotated with <code>:number</code>, <code>:integer</code>,
<code>:currency</code>, <code>:percent</code> or <code>:unit</code>
(inline or through <code>.input</code> / <code>.local</code>) takes
<code>number</code>, <code>:datetime</code>, <code>:date</code> and
<code>:time</code> take <code>Date</code>, <code>:string</code> takes
<code>string</code>, option and markup variables
(<code>minimumFractionDigits=$digits</code>, <code>{#link
href=$url}</code>) are required too, <code>.local</code> variables are
not arguments, and <code>|quoted literals|</code> and <code>\{</code>
escapes are skipped.</li>
<li><code>interpolationFormatTypeMap</code> overrides a type by ICU
format or MF2 function name, e.g. <code>date: Date | number</code> or a
custom <code>uppercase: string</code>.</li>
<li>Applies to <code>t()</code>, <code>getFixedT()</code>,
<code>i18n.t</code>, key prefixes, namespaces, the selector API and
react-i18next's <code>Trans</code> <code>values</code>. Messages need
literal types, as the resources file from i18next-cli's
<code>types</code> command has them.</li>
<li>Type-check cost with 1,000 messages and one call each: 1.35s instead
of 0.86s with <code>false</code> (TypeScript 6), 0.5s instead of 0.26s
with TypeScript 7. Messages that no call uses cost nothing.</li>
</ul>
</li>
<li>fix(types): with the default (non-strict) key checks, an options
object with a missing or misspelled interpolation variable now reports
the missing variable (<code>Property 'name' is missing</code>) instead
of <code>'{ nmae: string }' is not assignable to type 'string'</code>
from the default-value overload.</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/i18next/i18next/commit/c46ea5c301c049d17e47412b1b64a94b54c1bb97"><code>c46ea5c</code></a>
26.5.2</li>
<li><a
href="https://github.com/i18next/i18next/commit/d798f0e703d49770f4016deb483945eecd3e59f3"><code>d798f0e</code></a>
fix(types): report the wrong t() option on TypeScript 7</li>
<li><a
href="https://github.com/i18next/i18next/commit/dabd9f60d849d66936baca4adbca7e349f459069"><code>dabd9f6</code></a>
26.5.1</li>
<li><a
href="https://github.com/i18next/i18next/commit/01c3852d941d2dad503ff477755e0c489f3d75ee"><code>01c3852</code></a>
perf(types): no quadratic type-check time for large namespaces</li>
<li><a
href="https://github.com/i18next/i18next/commit/64b9da8bfd6d1e2a58eef23ed885b5ab60a412f1"><code>64b9da8</code></a>
26.5.0</li>
<li><a
href="https://github.com/i18next/i18next/commit/2468227c924204a6fafcf78ff615d7a232e9a07a"><code>2468227</code></a>
feat(types): parseInterpolation 'icu' and 'mf2' type t() options from
ICU arg...</li>
<li>See full diff in <a
href="https://github.com/i18next/i18next/compare/v26.4.7...v26.5.2">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=i18next&package-manager=npm_and_yarn&previous-version=26.4.7&new-version=26.5.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

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-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

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)


</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
---
 package-lock.json | 2 +-
 package.json      | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/package-lock.json b/package-lock.json
index 0d9aea8c..1888b819 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -30,7 +30,7 @@
         "downshift": "^9.4.0",
         "events": "^3.3.0",
         "file-saver": "^2.0.5",
-        "i18next": "^26.4.7",
+        "i18next": "^26.5.2",
         "i18next-browser-languagedetector": "^8.2.1",
         "i18next-resources-to-backend": "^1.2.3",
         "json-stringify-pretty-compact": "^4.0.0",
diff --git a/package.json b/package.json
index 4f400613..eff5de29 100644
--- a/package.json
+++ b/package.json
@@ -48,7 +48,7 @@
     "downshift": "^9.4.0",
     "events": "^3.3.0",
     "file-saver": "^2.0.5",
-    "i18next": "^26.4.7",
+    "i18next": "^26.5.2",
     "i18next-browser-languagedetector": "^8.2.1",
     "i18next-resources-to-backend": "^1.2.3",
     "json-stringify-pretty-compact": "^4.0.0",