fix(deps): update dependency react-i18next to v17.0.7#1266
Open
renovate[bot] wants to merge 1 commit into
Open
fix(deps): update dependency react-i18next to v17.0.7#1266renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
| Duplication | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
renovate
Bot
force-pushed
the
renovate/react-i18next-17.x
branch
from
May 8, 2026 18:23
93089d7 to
b5c8e93
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
17.0.6→17.0.7Release Notes
i18next/react-i18next (react-i18next)
v17.0.7Compare Source
useTranslation([nsA, nsB, ...])now passes its full namespace list togetFixedTvia the newscopeNsopt (requiresi18next≥ v26.0.10). This makes selector calls with a secondary-namespace prefix resolve correctly under defaultnsMode:t($ => $.nsB.foo)previously missed silently because the boundnswas the primary string only and i18next's selector rewrite needed an array. Resolution semantics are unchanged — plaint('key')lookups still stay isolated to the primary namespace by default; usensMode: 'fallback'to opt into multi-ns fallback resolution as before. Fixes i18next#2429 foruseTranslation-based callers.Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.