Skip to content

deps(deps): bump i18next from 26.3.0 to 26.3.1 in the i18n group across 1 directory#56

Merged
komed3 merged 1 commit into
masterfrom
dependabot/npm_and_yarn/i18n-b06bd6a154
Jun 8, 2026
Merged

deps(deps): bump i18next from 26.3.0 to 26.3.1 in the i18n group across 1 directory#56
komed3 merged 1 commit into
masterfrom
dependabot/npm_and_yarn/i18n-b06bd6a154

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 8, 2026

Copy link
Copy Markdown
Contributor

Bumps the i18n group with 1 update in the / directory: i18next.

Updates i18next from 26.3.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).
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).
Commits

@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Jun 8, 2026
Bumps the i18n group with 1 update in the / directory: [i18next](https://github.com/i18next/i18next).


Updates `i18next` from 26.3.0 to 26.3.1
- [Release notes](https://github.com/i18next/i18next/releases)
- [Changelog](https://github.com/i18next/i18next/blob/master/CHANGELOG.md)
- [Commits](i18next/i18next@v26.3.0...v26.3.1)

---
updated-dependencies:
- dependency-name: i18next
  dependency-version: 26.3.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: i18n
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title deps(deps): bump i18next from 26.3.0 to 26.3.1 in the i18n group deps(deps): bump i18next from 26.3.0 to 26.3.1 in the i18n group across 1 directory Jun 8, 2026
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/i18n-b06bd6a154 branch from ba9db60 to 36ed179 Compare June 8, 2026 20:30
@komed3 komed3 merged commit d5bab80 into master Jun 8, 2026
1 check passed
@dependabot dependabot Bot deleted the dependabot/npm_and_yarn/i18n-b06bd6a154 branch June 8, 2026 20:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant