From 4e2a82487aa3c3bf35d95ae685d4c571650dac4a Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Thu, 18 Jun 2026 15:12:39 -0700
Subject: [PATCH] build(deps): bump i18next from 26.2.0 to 26.3.1 (#7750)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Bumps [i18next](https://github.com/i18next/i18next) from 26.2.0 to
26.3.1.
Release notes
Sourced from i18next's
releases.
v26.3.1
- fix(types):
t() with a keyPrefix no longer
pollutes its return type with sibling keys' values. A regression in
26.3.0 — the [Res] extends [never] guards added to
KeysBuilderWithReturnObjects /
KeysBuilderWithoutReturnObjects turned the builders into
deferred conditional types, so KeyPrefix<Ns> stopped
resolving to a literal union and keyPrefix inference
widened to the whole namespace. Symptom: useTranslation(ns, {
keyPrefix: 'a.b' }) then t('title') would resolve to
'<a.b>.title' | '<other.path>.title' | ...
instead of just the scoped value. Affected every
react-i18next user using keyPrefix. Restored
to the eager 26.2.0 form. The same-namespace conflict handling from #2434
still works via _DropConflictKeys at the merge layer (in
options.d.ts). Thanks @aaronrosenthal
(#2436).
v26.3.0
- feat(types): introduce
ResourceNamespaceMap — a
separate mergeable augmentation surface for namespace resource types,
designed for monorepos where multiple packages each want to contribute
their own namespaces. Previously, every package had to coordinate on a
single CustomTypeOptions.resources declaration (or fall
back to typing dependency namespaces as any) because
resources is a single property of an interface and
TypeScript reports TS2717 when two declarations of the same property
disagree. The new interface merges naturally across declare module
'i18next' blocks, so each package can ship its own
i18next.d.ts independently. Per-property merge handles
same-namespace contributions from multiple packages, and
same-key/different-literal conflicts are silently dropped to avoid
poisoning t() overload resolution. Fully
backwards-compatible — existing CustomTypeOptions.resources
augmentations continue to work, and both surfaces can coexist. Scalar
options (defaultNS, returnNull,
enableSelector, etc.) still belong on
CustomTypeOptions. Thanks @sh3xu (#2434).
Fixes #2409.
Changelog
Sourced from i18next's
changelog.
26.3.1
- fix(types):
t() with a keyPrefix no longer
pollutes its return type with sibling keys' values. A regression in
26.3.0 — the [Res] extends [never] guards added to
KeysBuilderWithReturnObjects /
KeysBuilderWithoutReturnObjects turned the builders into
deferred conditional types, so KeyPrefix<Ns> stopped
resolving to a literal union and keyPrefix inference
widened to the whole namespace. Symptom: useTranslation(ns, {
keyPrefix: 'a.b' }) then t('title') would resolve to
'<a.b>.title' | '<other.path>.title' | ...
instead of just the scoped value. Affected every
react-i18next user using keyPrefix. Restored
to the eager 26.2.0 form. The same-namespace conflict handling from #2434
still works via _DropConflictKeys at the merge layer (in
options.d.ts). Thanks @aaronrosenthal
(#2436).
26.3.0
- feat(types): introduce
ResourceNamespaceMap — a
separate mergeable augmentation surface for namespace resource types,
designed for monorepos where multiple packages each want to contribute
their own namespaces. Previously, every package had to coordinate on a
single CustomTypeOptions.resources declaration (or fall
back to typing dependency namespaces as any) because
resources is a single property of an interface and
TypeScript reports TS2717 when two declarations of the same property
disagree. The new interface merges naturally across declare module
'i18next' blocks, so each package can ship its own
i18next.d.ts independently. Per-property merge handles
same-namespace contributions from multiple packages, and
same-key/different-literal conflicts are silently dropped to avoid
poisoning t() overload resolution. Fully
backwards-compatible — existing CustomTypeOptions.resources
augmentations continue to work, and both surfaces can coexist. Scalar
options (defaultNS, returnNull,
enableSelector, etc.) still belong on
CustomTypeOptions. Thanks @sh3xu (#2434).
Fixes #2409.
Commits
7bdb5d7
26.3.1a655e32
changelog: 26.3.1 entry for #243657ed812
fix(types): keyPrefix no longer pollutes t() return type with sibling
keys (#...bdf651c
26.3.0988a362
changelog: 26.3.0 entry for #2434159506c
feat(types): introduce ResourceNamespaceMap for monorepo namespace
augmentati...df68b1f
ci: restore JSR publishing via GitHub Actions OIDC- See full diff in compare
view
[](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)
---
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 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)
Signed-off-by: dependabot[bot]
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
---
pnpm-lock.yaml | 16 ++++++++--------
ui/package.json | 2 +-
2 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
index 4ffa1d0a..c9299bea 100644
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@@ -870,8 +870,8 @@ importers:
specifier: ^0.2.0
version: 0.2.0
i18next:
- specifier: ^26.1.0
- version: 26.2.0(typescript@5.9.3)
+ specifier: ^26.3.1
+ version: 26.3.1(typescript@5.9.3)
lexical:
specifier: 0.35.0
version: 0.35.0
@@ -892,7 +892,7 @@ importers:
version: 19.2.4(react@19.2.4)
react-i18next:
specifier: ^17.0.7
- version: 17.0.8(i18next@26.2.0(typescript@5.9.3))(react-dom@19.2.4(react@19.2.4))(react@19.2.4)(typescript@5.9.3)
+ version: 17.0.8(i18next@26.3.1(typescript@5.9.3))(react-dom@19.2.4(react@19.2.4))(react@19.2.4)(typescript@5.9.3)
react-markdown:
specifier: ^10.1.0
version: 10.1.0(@types/react@19.2.14)(react@19.2.4)
@@ -6100,8 +6100,8 @@ packages:
humanize-ms@1.2.1:
resolution: {integrity: sha512-Fl70vYtsAFb/C06PTS9dZBo7ihau+Tu/DNCk/OyHhea07S+aeMWpFFkUaXRa8fI+ScZbEI8dfSxwY7gxZ9SAVQ==}
- i18next@26.2.0:
- resolution: {integrity: sha512-zwBHldHdTmwN7r6UNc7lC6GWNN+YYg3DrRSeHR5PRRBf5QnJZcYHrQc0uaU26qZeYxR7iFZD+Y315dPnKP47wA==}
+ i18next@26.3.1:
+ resolution: {integrity: sha512-txQqd5EULsqEh9OJqRH15aCaOuy/nLJyhw5EHCSKLKJE1aBbb3Zve2+uQIxgWhPm1QqUQoWyQBm2kfmmIrzkcQ==}
peerDependencies:
typescript: ^5 || ^6
peerDependenciesMeta:
@@ -13780,7 +13780,7 @@ snapshots:
ms: 2.1.3
optional: true
- i18next@26.2.0(typescript@5.9.3):
+ i18next@26.3.1(typescript@5.9.3):
optionalDependencies:
typescript: 5.9.3
@@ -15185,11 +15185,11 @@ snapshots:
dependencies:
react: 19.2.4
- react-i18next@17.0.8(i18next@26.2.0(typescript@5.9.3))(react-dom@19.2.4(react@19.2.4))(react@19.2.4)(typescript@5.9.3):
+ react-i18next@17.0.8(i18next@26.3.1(typescript@5.9.3))(react-dom@19.2.4(react@19.2.4))(react@19.2.4)(typescript@5.9.3):
dependencies:
'@babel/runtime': 7.29.2
html-parse-stringify: 3.0.1
- i18next: 26.2.0(typescript@5.9.3)
+ i18next: 26.3.1(typescript@5.9.3)
react: 19.2.4
use-sync-external-store: 1.6.0(react@19.2.4)
optionalDependencies:
diff --git a/ui/package.json b/ui/package.json
index bfd025fa..9028a335 100644
--- a/ui/package.json
+++ b/ui/package.json
@@ -53,7 +53,7 @@
"clsx": "^2.1.1",
"cmdk": "^1.1.1",
"hermes-paperclip-adapter": "^0.2.0",
- "i18next": "^26.1.0",
+ "i18next": "^26.3.1",
"lexical": "0.35.0",
"lucide-react": "^0.574.0",
"mermaid": "^11.12.0",