Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 1, 2026

This PR contains the following updates:

Package Change Age Confidence
i18next (source) ^23.7.16^25.0.0 age confidence

Release Notes

i18next/i18next (i18next)

v25.7.3

Compare Source

v25.7.2

Compare Source

  • fix: Invalid overwrite of default value for overloadTranslationOptionHandler 2374.

v25.7.1

Compare Source

  • TS: remove wrong signature 2372.

v25.7.0

Compare Source

  • Enhance cloneInstance to create a new interpolator if interpolation options are passed in. This will address 2371.

v25.6.3

Compare Source

  • chore: dependency updates 2368

v25.6.2

Compare Source

  • types: export InterpolationMap

v25.6.1

Compare Source

  • fix: createInstance does not exist on an instance #​2366

v25.6.0

Compare Source

  • feat: exists() method now respects returnObjects option - returns false when accessing an object key with returnObjects: false, enabling detection of object vs string keys 2359

    Note: This is a potential behavior change. If you were previously calling exists() with returnObjects: false on object keys, those calls will now return false instead of true. This enables developers to detect whether a key points to an object or string value.

v25.5.3

Compare Source

  • export esm type declaration for keyFromSelector 2356

v25.5.2

Compare Source

  • fix last change => for cjs there is just 1 default export, no named exports, fixes 2348

v25.5.1

Compare Source

  • export keyFromSelector from index.cjs 2347

v25.5.0

Compare Source

  • export keyFromSelector function for testing purposes 2346

v25.4.2

Compare Source

  • fix: enableSelector: true doesn't work with custom keySeparator 2341

v25.4.1

Compare Source

  • fix: KeyPrefix not working with new selector api 2340

v25.4.0

Compare Source

  • add new selector API to improve TypeScript IDE performance 2322
    • To enable it, set enableSelector: true in your configuration options
    • With enableSelector: "optimize", i18next can now handle translation dictionaries of any size, without affecting IDE performance or build times
    • To assist with the migration, we've published the following packages:

v25.3.6

Compare Source

  • improve fix: Ordinals and non-ordinals don't work together 2337

v25.3.5

Compare Source

  • fix: Ordinals and non-ordinals don't work together 2337

v25.3.4

Compare Source

  • remove unnecessary debug logs

v25.3.3

Compare Source

  • fix: Brackets breaking nesting interpolation 2336

v25.3.2

Compare Source

  • fix dir() for non-Intl language codes 2330

v25.3.1

Compare Source

  • warn if legacy interpolation.format function is still used

v25.3.0

Compare Source

  • feat: support formatting function with plural and interpolation 2325
  • fix dir() for Latn language codes 2324

v25.2.1

Compare Source

  • streamline fallbackLng option of t call with the init options 2312

v25.2.0

Compare Source

  • introduce cacheInBuiltFormats option to address 2227

v25.1.3

Compare Source

  • Ensure nsSeparator is respected when appendNamespaceToMissingKey is true 2311, fixes 2310

v25.1.2

Compare Source

  • do not mutate t options, fixes 2307

v25.1.1

Compare Source

  • fix options type for parseMissingKeyHandler

v25.1.0

Compare Source

  • feat: parseMissingKeyHandler now takes options as parameter like in missingKeyHandler 2304

v25.0.2

Compare Source

  • fix cloneInstance with forkResourceStore: true addresses 2303

v25.0.1

Compare Source

  • optimize changeLanguage to correctly use getBestMatchFromCodes (string or array) 2299 and improve resolvedLanguage set for non canonical codes

v25.0.0

Compare Source

This is a potentially breaking release:

  • fix multiple changeLanguage call that may have result in wrong order in previous versions 1605 2298
  • adapt changeLanguage to always (string or array) use getBestMatchFromCodes 2299
  • getBestMatchFromCodes now tries to fallback to language code with same script 2299

v24.2.3

Compare Source

v24.2.2

Compare Source

  • fix: Interpolation fails with arrays (TypeError) and doesn't work with objects in defaultValue 1829

v24.2.1

Compare Source

  • Standardize null/undefined checks across codebase 2275
  • fix(typescript): make TFunction augmentable again 2279, fixes 2278

v24.2.0

Compare Source

  • feat(typescript): Add strictKeyChecks option to enforce checking key existence when defaultValue is used 2274, fixes 2043

v24.1.2

Compare Source

  • optimize fix: Bug Report: Unsafe Behavior in i18n.t Function Leading to Potential Code Execution 2273

v24.1.1

Compare Source

  • fix: Bug Report: Unsafe Behavior in i18n.t Function Leading to Potential Code Execution 2273

v24.1.0

Compare Source

  • try to address 2270 by cloning the store data 2271

v24.0.5

Compare Source

  • remove extra log for 2268

v24.0.4

Compare Source

  • simplify fix: incorrect locale detected 2268

v24.0.3

Compare Source

  • fix: incorrect locale detected 2268
  • fix: Intl.getCanonicalLocales throws with custom regions 2267

v24.0.2

Compare Source

  • if no Intl api, log error and use dummy rule

v24.0.1

Compare Source

  • early return and log error, if no Intl api

v24.0.0

Compare Source

This is a major breaking release:

  • remove support for older environments
  • remove old i18next JSON formats
  • remove support for compatibility to v1 API
  • Intl API is mandatory now and will not fallback anymore
  • possible compatibility layer for older formats: test/compatibility/v4/v4Compatibility.js
  • rename initImmediate to initAsync
  • fallback to dev language if plural rule not found
  • Dropped support for Node.js < v14
  • remove TypeScript v4 support. TypeScript v5 is now an optional peer dependency
  • addresses

➡️ check out the migration guide


Configuration

📅 Schedule: Branch creation - "every 3 months on the first day of the month" in timezone Europe/Stockholm, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented Jan 1, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: client/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: onelist-client@1.0.0
npm error Found: typescript@4.9.5
npm error node_modules/typescript
npm error   peer typescript@">= 2.7" from fork-ts-checker-webpack-plugin@6.5.3
npm error   node_modules/fork-ts-checker-webpack-plugin
npm error     fork-ts-checker-webpack-plugin@"^6.5.0" from react-dev-utils@12.0.1
npm error     node_modules/react-dev-utils
npm error       react-dev-utils@"^12.0.1" from react-scripts@5.0.1
npm error       node_modules/react-scripts
npm error         dev react-scripts@"5.0.1" from the root project
npm error   typescript@"^4.5.4" from prettier-eslint@15.0.1
npm error   node_modules/prettier-eslint
npm error     dev prettier-eslint@"15.0.1" from the root project
npm error   2 more (react-scripts, tsutils)
npm error
npm error Could not resolve dependency:
npm error i18next@"^25.0.0" from the root project
npm error
npm error Conflicting peer dependency: typescript@5.9.3
npm error node_modules/typescript
npm error   peerOptional typescript@"^5" from i18next@25.7.3
npm error   node_modules/i18next
npm error     i18next@"^25.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-01-01T18_39_18_571Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-01-01T18_39_18_571Z-debug-0.log

@renovate
Copy link
Contributor Author

renovate bot commented Jan 4, 2026

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 25.x releases. But if you manually upgrade to 25.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/i18next-25.x branch January 4, 2026 13:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants