[PR #377] chore(deps): Bump react-i18next from 16.6.6 to 17.0.4 #377

New issue

Open

opened 2026-05-06 12:16:39 +02:00 by BreizhHardware · 0 comments

BreizhHardware commented

2026-05-06 12:16:39 +02:00

Owner

📋 Pull Request Information

Original PR: https://github.com/BreizhHardware/portfolio/pull/377
Author: @dependabot[bot]
Created: 4/20/2026
Status: 🔄 Open

Base: dev ← Head: dependabot/npm_and_yarn/dev/react-i18next-17.0.4

📝 Commits (1)

f726691 chore(deps): Bump react-i18next from 16.6.6 to 17.0.4

📊 Changes

2 files changed (+7 additions, -7 deletions)

View changed files

📝 package.json (+1 -1)
📝 pnpm-lock.yaml (+6 -6)

📄 Description

Bumps react-i18next from 16.6.6 to 17.0.4.

Changelog

Sourced from react-i18next's changelog.

17.0.4

fix: avoid React does not recognize the 'i18nIsDynamicList' prop on a DOM element warning 1915

17.0.3

fix: avoid invalid prop on React.Fragment inside <Trans /> 1914

17.0.2

fix(types): values prop on <Trans /> now only requires interpolation variables for the specific i18nKey, not all variables in the namespace 1913

17.0.1

chore: bump minimum i18next peer dependency to >= 26.0.1 (forgot to do it in last version)

fix: migrate test setup from removed legacy interpolation.format to i18n.services.formatter.add() (i18next v26)

17.0.0

Potentially breaking changes

fix: transKeepBasicHtmlNodesFor now correctly preserves HTML tag names when children contain interpolations or mixed content 230

Previously, <strong>{{name}}</strong> was incorrectly serialized as <1>{{name}}</1> — the tag name was only preserved for plain string children

This bug existed since the feature was introduced and affects auto-generated keys (when no explicit i18nKey is provided)

If you rely on auto-generated Trans keys containing indexed tags for kept HTML elements with interpolation children, you will need to update your translation files

Other changes

updated dev dependencies (vitest, rollup plugins, happy-dom, typescript, etc.)

Commits

a398b76 17.0.4
c96f7bc fix: avoid `React does not recognize the i18nIsDynamicList prop on a DOM elem...
fe111f7 17.0.3
e7419b8 fix: avoid invalid prop on React.Fragment inside \<Trans /> #1914
4d62f86 17.0.2
61fe80c fix(types): values prop on \<Trans /> now only requires interpolation vari...
b58d5a5 l10n: add Swedish language support to examples (#1912)
2321496 17.0.1
7e656b5 chore: bump minimum i18next peer dependency
dfc350b upate github actions
Additional commits viewable in compare view

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 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 <dependency name> 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)

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/BreizhHardware/portfolio/pull/377 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 4/20/2026 **Status:** 🔄 Open **Base:** `dev` ← **Head:** `dependabot/npm_and_yarn/dev/react-i18next-17.0.4` --- ### 📝 Commits (1) - [`f726691`](https://github.com/BreizhHardware/portfolio/commit/f7266913325e6a0492bec78a059e59da80f0e522) chore(deps): Bump react-i18next from 16.6.6 to 17.0.4 ### 📊 Changes **2 files changed** (+7 additions, -7 deletions) <details> <summary>View changed files</summary> 📝 `package.json` (+1 -1) 📝 `pnpm-lock.yaml` (+6 -6) </details> ### 📄 Description Bumps [react-i18next](https://github.com/i18next/react-i18next) from 16.6.6 to 17.0.4. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/i18next/react-i18next/blob/master/CHANGELOG.md">react-i18next's changelog</a>.</em></p> <blockquote> <h2>17.0.4</h2> <ul> <li>fix: avoid <code>React does not recognize the 'i18nIsDynamicList' prop on a DOM element</code> warning <a href="https://redirect.github.com/i18next/react-i18next/issues/1915">1915</a></li> </ul> <h2>17.0.3</h2> <ul> <li>fix: avoid invalid prop on <code>React.Fragment</code> inside <code><Trans /></code> <a href="https://redirect.github.com/i18next/react-i18next/issues/1914">1914</a></li> </ul> <h2>17.0.2</h2> <ul> <li>fix(types): <code>values</code> prop on <code><Trans /></code> now only requires interpolation variables for the specific <code>i18nKey</code>, not all variables in the namespace <a href="https://redirect.github.com/i18next/react-i18next/issues/1913">1913</a></li> </ul> <h2>17.0.1</h2> <ul> <li>chore: bump minimum i18next peer dependency to <code>>= 26.0.1</code> <em>(forgot to do it in last version)</em></li> <li>fix: migrate test setup from removed legacy <code>interpolation.format</code> to <code>i18n.services.formatter.add()</code> (i18next v26)</li> </ul> <h2>17.0.0</h2> <h3>Potentially breaking changes</h3> <ul> <li>fix: <code>transKeepBasicHtmlNodesFor</code> now correctly preserves HTML tag names when children contain interpolations or mixed content <a href="https://redirect.github.com/i18next/i18next-cli/issues/230">230</a> <ul> <li>Previously, <code><strong>{{name}}</strong></code> was incorrectly serialized as <code><1>{{name}}</1></code> — the tag name was only preserved for plain string children</li> <li>This bug existed since the feature was introduced and affects auto-generated keys (when no explicit <code>i18nKey</code> is provided)</li> <li>If you rely on auto-generated Trans keys containing indexed tags for kept HTML elements with interpolation children, you will need to update your translation files</li> </ul> </li> </ul> <h3>Other changes</h3> <ul> <li>updated dev dependencies (vitest, rollup plugins, happy-dom, typescript, etc.)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/i18next/react-i18next/commit/a398b7692bab6737dfaf9f8e75f874388b332ba4"><code>a398b76</code></a> 17.0.4</li> <li><a href="https://github.com/i18next/react-i18next/commit/c96f7bc219994731c5606edb1c1f4dd6c04ea98b"><code>c96f7bc</code></a> fix: avoid `React does not recognize the i18nIsDynamicList prop on a DOM elem...</li> <li><a href="https://github.com/i18next/react-i18next/commit/fe111f751842c1ab2566d9ecfa5d41f796f77ae7"><code>fe111f7</code></a> 17.0.3</li> <li><a href="https://github.com/i18next/react-i18next/commit/e7419b86966c1b0580f60022edfca99fe1998c16"><code>e7419b8</code></a> fix: avoid invalid prop on <code>React.Fragment</code> inside <code>\<Trans /></code> <a href="https://redirect.github.com/i18next/react-i18next/issues/1914">#1914</a></li> <li><a href="https://github.com/i18next/react-i18next/commit/4d62f869053355821249c6235c2ded6e8e3ea492"><code>4d62f86</code></a> 17.0.2</li> <li><a href="https://github.com/i18next/react-i18next/commit/61fe80c53fff86bb276ab9854ef33a3228e88147"><code>61fe80c</code></a> fix(types): <code>values</code> prop on <code>\<Trans /></code> now only requires interpolation vari...</li> <li><a href="https://github.com/i18next/react-i18next/commit/b58d5a57b851871a85bfc4c2f530cf2b78cbbbb3"><code>b58d5a5</code></a> l10n: add Swedish language support to examples (<a href="https://redirect.github.com/i18next/react-i18next/issues/1912">#1912</a>)</li> <li><a href="https://github.com/i18next/react-i18next/commit/23214960e3ead0b6774a1a0cb40387d41868da60"><code>2321496</code></a> 17.0.1</li> <li><a href="https://github.com/i18next/react-i18next/commit/7e656b567125b059738ccd6f79b45de3767a8df4"><code>7e656b5</code></a> chore: bump minimum i18next peer dependency</li> <li><a href="https://github.com/i18next/react-i18next/commit/dfc350b2c465a7e0283c4fa5c6d83e3d447fc87a"><code>dfc350b</code></a> upate github actions</li> <li>Additional commits viewable in <a href="https://github.com/i18next/react-i18next/compare/v16.6.6...v17.0.4">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=react-i18next&package-manager=npm_and_yarn&previous-version=16.6.6&new-version=17.0.4)](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) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 <dependency name> 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) </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>