Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 27, 2025

This PR contains the following updates:

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

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

i18next/i18next (i18next)

v25.7.4

Compare Source

  • fix: Interpolation breaks when cloning an instance 2376

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

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 Nov 27, 2025

⚠️ 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: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm warn Unknown project config "always-auth". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @spartacus/[email protected]
npm error Found: [email protected]
npm error node_modules/i18next
npm error   i18next@"^25.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer i18next@"^24.2.1" from @spartacus/[email protected]
npm error node_modules/@spartacus/core
npm error   @spartacus/core@"~2211.43.0" from the root project
npm error   peer @spartacus/core@"2211.43.0" from @spartacus/[email protected]
npm error   node_modules/@spartacus/asm
npm error     @spartacus/asm@"~2211.43.0" from the root project
npm error   13 more (@spartacus/cart, @spartacus/checkout, ...)
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/i18next
npm error   peer i18next@"^24.2.1" from @spartacus/[email protected]
npm error   node_modules/@spartacus/core
npm error     @spartacus/core@"~2211.43.0" from the root project
npm error     peer @spartacus/core@"2211.43.0" from @spartacus/[email protected]
npm error     node_modules/@spartacus/asm
npm error       @spartacus/asm@"~2211.43.0" from the root project
npm error     13 more (@spartacus/cart, @spartacus/checkout, ...)
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-08T21_06_50_426Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-01-08T21_06_50_426Z-debug-0.log

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.

1 participant