mirror of
https://github.com/evroon/bracket.git
synced 2026-04-20 07:16:59 -04:00
Bumps [i18next](https://github.com/i18next/i18next) from 25.8.0 to 25.10.5. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/i18next/i18next/releases">i18next's releases</a>.</em></p> <blockquote> <h2>v25.10.5</h2> <ul> <li>feat(types): selector functions as <code>keyPrefix</code> in <code>getFixedT</code> now provide full type-safe key narrowing — the returned <code>t</code> function is scoped to the prefix subtree <a href="https://redirect.github.com/i18next/i18next/issues/2367">2367</a></li> </ul> <h2>v25.10.4</h2> <ul> <li>feat(types): i18nKey of <code><Trans i18nKey={sk} /></code> to accept a <code>SelectorKey</code> <a href="https://redirect.github.com/i18next/i18next/issues/2364">2364</a></li> </ul> <h2>v25.10.3</h2> <ul> <li>check also for I18NEXT_NO_SUPPORT_NOTICE env variable</li> </ul> <h2>v25.10.2</h2> <ul> <li>feat(types): <code>keyFromSelector</code> is now type-safe — the selector callback is constrained against your resource definitions, catching invalid keys at compile time. Supports optional <code>ns</code> and <code>keyPrefix</code> options for non-default namespace/prefix contexts <a href="https://redirect.github.com/i18next/i18next/issues/2364">2364</a></li> </ul> <h2>v25.10.1</h2> <ul> <li>fix(types): <code>FilterKeys</code> now correctly excludes base keys that have context variants when the provided context doesn't match any of them (e.g. key <code>some</code> with variant <code>some_me</code> is no longer accessible with <code>context="one"</code>)</li> </ul> <h2>v25.10.0</h2> <ul> <li>feat(types): <code>keyFromSelector</code> now returns a branded <code>SelectorKey</code> type that <code>t()</code> accepts directly, enabling pre-computed and reusable translation keys <a href="https://redirect.github.com/i18next/i18next/issues/2364">2364</a></li> <li>feat: support selector syntax for <code>keyPrefix</code> in <code>getFixedT</code> and per-call options <a href="https://redirect.github.com/i18next/i18next/issues/2367">2367</a></li> <li>feat(types): interpolation values are now automatically typed based on built-in format specifiers — <code>{{val, number}}</code> requires <code>number</code>, <code>{{val, datetime}}</code> requires <code>Date</code>, <code>{{name}}</code> requires <code>string</code>, etc. Custom formatters can be typed via <code>interpolationFormatTypeMap</code> in <code>CustomTypeOptions</code> <a href="https://redirect.github.com/i18next/i18next/issues/2378">2378</a></li> <li>fix(types): <code>FilterKeys</code> in selector mode now preserves non-context, non-plural leaf keys when <code>context</code> is provided, fixing incorrect type narrowing when combining <code>returnObjects: true</code> with <code>context</code> <a href="https://redirect.github.com/i18next/i18next/issues/2398">2398</a></li> </ul> <h2>v25.9.0</h2> <ul> <li>feat(types): selector API now enforces <code>{ count: number }</code> when a key resolves to plural forms <a href="https://redirect.github.com/i18next/i18next/issues/2373">2373</a></li> <li>fix(types): string unions with invalid members are now correctly detected as type errors when used as context option <a href="https://redirect.github.com/i18next/i18next/issues/2172">2172</a></li> </ul> <h2>v25.8.20</h2> <ul> <li> <ul> <li>fix: <code>getFixedT()</code> selector now resolves namespaces against the effective <code>ns</code> rather than the global init options <a href="https://redirect.github.com/i18next/i18next/issues/2406">#2406</a></li> </ul> </li> </ul> <h2>v25.8.19</h2> <ul> <li>fix: selector API namespace resolution regression for single-string <code>ns</code> and primary namespace in array <a href="https://redirect.github.com/i18next/i18next/issues/2405">#2405</a>. Reverts the broad namespace-prefix rewrite from v25.8.15 and replaces it with a targeted fix that only rewrites paths starting with a secondary namespace in a multi-namespace array, matching the type-level contract of <code>GetSource</code></li> </ul> <h2>v25.8.18</h2> <ul> <li>improve selector api to accept array of selector functions, analogous to array of keys <a href="https://redirect.github.com/i18next/i18next/issues/2404">2404</a></li> </ul> <h2>v25.8.17</h2> <ul> <li>update deps</li> </ul> <h2>v25.8.16</h2> <ul> <li>fix(types): <code>on()</code> method now correctly returns <code>this</code> instead of <code>void</code>, matching the runtime behavior and enabling proper method chaining in TypeScript</li> </ul> <h2>v25.8.15</h2> <ul> <li>fix: Selector API unable to resolve namespaces <a href="https://redirect.github.com/i18next/i18next/issues/2402">#2402</a></li> </ul> <h2>v25.8.14</h2> <ul> <li>fix: getCleanedCode now replaces all underscores</li> </ul> <h2>v25.8.13</h2> <ul> <li>improve support notice shown logic</li> </ul> <h2>v25.8.12</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/i18next/i18next/blob/master/CHANGELOG.md">i18next's changelog</a>.</em></p> <blockquote> <h2>25.10.5</h2> <ul> <li>feat(types): selector functions as <code>keyPrefix</code> in <code>getFixedT</code> now provide full type-safe key narrowing — the returned <code>t</code> function is scoped to the prefix subtree <a href="https://redirect.github.com/i18next/i18next/issues/2367">2367</a></li> </ul> <h2>25.10.4</h2> <ul> <li>feat(types): <code>exists()</code> is now a type guard that narrows the key to <code>SelectorKey</code>, so a validated key can be passed directly to <code>t()</code> <a href="https://redirect.github.com/i18next/i18next/issues/2364">2364</a></li> </ul> <h2>25.10.3</h2> <ul> <li>check also for I18NEXT_NO_SUPPORT_NOTICE env variable</li> </ul> <h2>25.10.2</h2> <ul> <li>feat(types): <code>keyFromSelector</code> is now type-safe — the selector callback is constrained against your resource definitions, catching invalid keys at compile time. Supports optional <code>ns</code> and <code>keyPrefix</code> options for non-default namespace/prefix contexts <a href="https://redirect.github.com/i18next/i18next/issues/2364">2364</a></li> </ul> <h2>25.10.1</h2> <ul> <li>fix(types): <code>FilterKeys</code> now correctly excludes base keys that have context variants when the provided context doesn't match any of them (e.g. key <code>some</code> with variant <code>some_me</code> is no longer accessible with <code>context="one"</code>)</li> </ul> <h2>25.10.0</h2> <ul> <li>feat(types): <code>keyFromSelector</code> now returns a branded <code>SelectorKey</code> type that <code>t()</code> accepts directly, enabling pre-computed and reusable translation keys <a href="https://redirect.github.com/i18next/i18next/issues/2364">2364</a></li> <li>feat: support selector syntax for <code>keyPrefix</code> in <code>getFixedT</code> and per-call options <a href="https://redirect.github.com/i18next/i18next/issues/2367">2367</a></li> <li>feat(types): interpolation values are now automatically typed based on built-in format specifiers — <code>{{val, number}}</code> requires <code>number</code>, <code>{{val, datetime}}</code> requires <code>Date</code>, <code>{{name}}</code> requires <code>string</code>, etc. Custom formatters can be typed via <code>interpolationFormatTypeMap</code> in <code>CustomTypeOptions</code> <a href="https://redirect.github.com/i18next/i18next/issues/2378">2378</a></li> <li>fix(types): <code>FilterKeys</code> in selector mode now preserves non-context, non-plural leaf keys when <code>context</code> is provided, fixing incorrect type narrowing when combining <code>returnObjects: true</code> with <code>context</code> <a href="https://redirect.github.com/i18next/i18next/issues/2398">2398</a></li> </ul> <h2>25.9.0</h2> <ul> <li>feat(types): selector API now enforces <code>{ count: number }</code> when a key resolves to plural forms <a href="https://redirect.github.com/i18next/i18next/issues/2373">2373</a></li> <li>fix(types): string unions with invalid members are now correctly detected as type errors when used as context option <a href="https://redirect.github.com/i18next/i18next/issues/2172">2172</a></li> </ul> <h2>25.8.20</h2> <ul> <li> <ul> <li>fix: <code>getFixedT()</code> selector now resolves namespaces against the effective <code>ns</code> rather than the global init options <a href="https://redirect.github.com/i18next/i18next/issues/2406">2406</a></li> </ul> </li> </ul> <h2>25.8.19</h2> <ul> <li>fix: selector API namespace resolution regression for single-string <code>ns</code> and primary namespace in array <a href="https://redirect.github.com/i18next/i18next/issues/2405">2405</a>. Reverts the broad namespace-prefix rewrite from v25.8.15 and replaces it with a targeted fix that only rewrites paths starting with a secondary namespace in a multi-namespace array, matching the type-level contract of <code>GetSource</code></li> </ul> <h2>25.8.18</h2> <ul> <li>improve selector api to accept array of selector functions, analogous to array of keys <a href="https://redirect.github.com/i18next/i18next/issues/2404">2404</a></li> </ul> <h2>25.8.17</h2> <ul> <li>update deps</li> </ul> <h2>25.8.16</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="83230b8f48"><code>83230b8</code></a> 25.10.5</li> <li><a href="79aa4d6245"><code>79aa4d6</code></a> address <a href="https://redirect.github.com/i18next/i18next/issues/2367">#2367</a></li> <li><a href="06f4ef70f2"><code>06f4ef7</code></a> address <a href="https://redirect.github.com/i18next/i18next/issues/2367">#2367</a></li> <li><a href="7902915328"><code>7902915</code></a> fix changelog</li> <li><a href="640ae9a2b2"><code>640ae9a</code></a> jsr update</li> <li><a href="de429ab17d"><code>de429ab</code></a> 25.10.4</li> <li><a href="3eb1b35b91"><code>3eb1b35</code></a> feat(types): i18nKey of <code>\<Trans i18nKey={sk} /></code> to accept a <code>SelectorKey</code> <a href="https://redirect.github.com/i18next/i18next/issues/2364">#2364</a></li> <li><a href="53220b7fb8"><code>53220b7</code></a> jsr update</li> <li><a href="908d0376bb"><code>908d037</code></a> 25.10.3</li> <li><a href="4e0b5da297"><code>4e0b5da</code></a> check also for I18NEXT_NO_SUPPORT_NOTICE env variable <a href="https://redirect.github.com/i18next/i18next/issues/2407">#2407</a></li> <li>Additional commits viewable in <a href="https://github.com/i18next/i18next/compare/v25.8.0...v25.10.5">compare view</a></li> </ul> </details> <br /> [](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> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>