Bumps the production-dependencies group with 4 updates: [@tauri-apps/plugin-notification](https://github.com/tauri-apps/plugins-workspace), [i18next](https://github.com/i18next/i18next), [lucide-react](https://github.com/lucide-icons/lucide/tree/HEAD/packages/lucide-react) and [react-i18next](https://github.com/i18next/react-i18next). Updates `@tauri-apps/plugin-notification` from 2.7.0 to 2.8.0

Release notes

Sourced from @tauri-apps/plugin-notification's releases.

notification-js v2.8.0

[2.8.0]

52fa7754 (#3738 by @renovate) Updated dependency rand to 0.10

feat

f36ba7ba (#3282 by @Et3rnel) Added chronometer support for Android notifications with when, usesChronometer, and chronometerCountDown options. This allows displaying an automatically updating elapsed time counter directly in the notification, useful for time-tracking apps, ongoing calls, or timers.

npm warn publish npm auto-corrected some errors in your package.json when publishing.  Please run "npm pkg fix" to address these errors.
npm warn publish errors corrected:
npm warn publish "repository" was changed from a string to an object
npm warn publish "repository.url" was normalized to "git+https://github.com/tauri-apps/plugins-workspace.git"
npm notice
npm notice 📦  @tauri-apps/plugin-notification@2.8.0
npm notice Tarball Contents
npm notice 888B LICENSE.spdx
npm notice 4.2kB README.md
npm notice 16.6kB dist-js/index.cjs
npm notice 27.0kB dist-js/index.d.ts
npm notice 16.2kB dist-js/index.js
npm notice 11B dist-js/init.d.ts
npm notice 663B package.json
npm notice Tarball Details
npm notice name: @tauri-apps/plugin-notification
npm notice version: 2.8.0
npm notice filename: tauri-apps-plugin-notification-2.8.0.tgz
npm notice package size: 11.4 kB
npm notice unpacked size: 65.7 kB
npm notice shasum: b37835641011d62d25bd923310d9e6217a1e5685
npm notice integrity: sha512-BB9Kk2emiNHyM[...]f0O8rtdW2F2dw==
npm notice total files: 7
npm notice
npm notice npm tokens that bypass 2FA are being restricted for account changes and direct publishing. Learn how to prepare: https://gh.io/npm-gat-bypass2fa-deprecation
npm notice Publishing to https://registry.npmjs.org/ with tag latest and public access
npm notice publish Signed provenance statement with source and build information from GitHub Actions
npm notice publish Provenance statement published to transparency log: https://search.sigstore.dev/?logIndex=3529333733
npm notice Your package is being processed and may take a few minutes to become available.
+ @tauri-apps/plugin-notification@2.8.0

notification v2.8.0

[2.8.0]

... (truncated)

Commits

6e2e7e4 publish new versions (#3070)
9a2c98f temp: remove updater changefiles
4a2ecb6 chore(deps): update rkyv, closes #3196
31415ef docs(shell): update example to include Encoding usage in Command::spawn (#3...
04b33ea chore(deps): update dependency typescript-eslint to v8.50.1 (#3181)
54e21f1 chore(deps): update dependency rollup to v4.54.0 (#3179)
d528c88 chore(deps): update dependency rollup to v4.53.5 (#3172)
69146fa chore(deps): update dependency rollup to v4.53.4 (#3167)
9f68f2d chore(deps): update dependency typescript-eslint to v8.50.0 (#3170)
3d0d2e0 fix(opener): ignore inAppBrowser on desktop (#3163)
Additional commits viewable in compare view

Updates `i18next` from 26.5.12 to 26.7.1

Release notes

Sourced from i18next's releases.

v26.7.1

fix: reloadResources() retries the bundles that failed to load. The load queue skipped them also when reloading, so a language whose first load failed (a backend or network outage at startup) stayed missing. i18next-http-backend 4.0.8, i18next-chained-backend 5.0.7 and i18next-locize-backend 10.0.5 reload through reloadResources() with i18next 26.7, so their reloadInterval no longer recovered from such a failure, as their own reload did before.

fix: reloadResources() without languages reloads the current languages and every language the backend loaded or tried to load, for the instance and its clones, as the API docs describe ("pass languages and namespaces if you don't want to reload all"). It reloaded only the current languages, so on a server (one clone per request with i18next-http-middleware) a backend's reloadInterval never refreshed the languages loaded for requests. It never requests cimode. With languages given, nothing changes.

v26.7.0

The last 26.x minor before v27, which follows in about a week. It adds the APIs v27 builds on, and with debug: true it warns wherever a setup relies on something v27 changes. Most of the v27 defaults are existing options, so you can try them now:
i18next.init({
 debug: true, // prints the warnings below
 fallbackLng: 'en', // v27: fallbackLng defaults to false, set your source language (no implicit 'dev')
 returnEmptyString: false, // v27 default: an empty string falls back like a missing key
 cleanCode: true, // close to v27, which canonicalizes codes without a region ('EN' becomes 'en')
});
declare module 'i18next' {
 interface CustomTypeOptions {
 strictInterpolationChecks: true; // v27 default
 returnEmptyString: false; // v27 default
 }
}
The other v27 changes (/ no longer escaped in values, a logger and post-processors per instance, the key instead of a sentence for an object hit, the dotted-language store calls and *Escaped options removed) have no switch; the debug warnings below show where they apply.

feat: with the default skipOnVariables: true, a missing interpolation variable is now logged in debug mode, once per string and variable: missed to pass in variable name for interpolating Hello {{name}}. The raw {{name}} reached the UI without any log line, even with debug: true, because the warning only ran with skipOnVariables: false. A variable passed as undefined and a missingInterpolationHandler still log nothing.

feat: i18next.hydrate(resources, lng) puts resources rendered on the server into the store and changes to the server's language, each only the first time. It does what react-i18next's useSSR did by writing resourceStore.data, options.ns, isInitialized, initializedStoreOnce and initializedLanguageOnce directly, and sets the same flags, so integrations can switch to it and stay compatible with code that still reads or writes them. On a clone it does nothing, as useSSR does: a clone shares its parent's store (one clone per request with i18next-http-middleware). Called before init(), it logs a warning and changes nothing.

feat: services.utils.reloadResources() lets a backend reload its bundles through i18next (as i18next.reloadResources(), with retries and the loaded event), instead of calling backendConnector.read() and loaded() itself as the reloadInterval of i18next-http-backend and i18next-chained-backend does. Without languages (no lng, no detector, the default fallbackLng), reloadResources() reloads nothing instead of throwing Cannot read properties of undefined (reading 'forEach'); a backend that also reloads preload passes its languages.

feat: backends and async language detectors can declare their calling convention with callbackApi (an instance or static property). true: read(language, namespace, callback), create(languages, namespace, key, fallbackValue, callback, options) and detect(callback); false: they return a promise or a value, and create gets the options as its fifth argument. Without it, i18next keeps guessing from the number of parameters (Function.length), which default and rest parameters change: i18next-chained-backend's create(..., clb = () => {}, opts = {}) has length 4 and never got its options (isUpdate), and i18next-http-backend's callback form of create has length 5, the length reserved for the callback-less form. Guessing is deprecated: in debug mode an unmarked backend or async detector logs a deprecation warning, once per init().

feat: isSafeLanguageCode(code) is exported for plugins that take a language from a request, a URL or storage: letters, digits, -, _, @ and . (no ..), at most 128 characters, not a prototype key. It is not a BCP 47 check, so en_US, zh_Hant_TW, sr@latin and de_DE.UTF-8 pass; markup, slashes and spaces do not. The language detector, i18next-http-middleware and i18next-http-backend each have their own rule today.

feat: use() logs a warning in debug mode when a second backend, language detector, i18nFormat or formatter replaces the first one; only one of each is used per instance, and losing an ICU setup this way was silent. As use() usually runs before init(), the warning is printed once init() has set up the logger.

feat(types): ParseKeysWithoutVariables<Ns, KPrefix>, the keys t() takes without options: their string has no variables, and a plural key is left out when its forms take count. A wrapper typed with it, like (key: ParseKeysWithoutVariables<'common'>) => t(key), compiles with strictInterpolationChecks without a cast.

feat(types): defaultVariables in CustomTypeOptions declares the variables interpolation.defaultVariables fills in at runtime (defaultVariables: { appName: string }). They become optional in the t() options, also with strictInterpolationChecks; passed, they keep their type.

feat(types): interpolationFormatSeparator in CustomTypeOptions for a custom interpolation.formatSeparator: the types split {{price, currency}} at a hard-coded ,, so with formatSeparator: ';' the format was not recognized. The per-call skipInterpolation option is typed, and returnedObjectHandler may return a value (what it returns is what t() returns; it was typed as returning void).

feat(types): SelectorFn, ApplyTarget, ConstrainTarget and GetSource are exported on purpose, under their current names. react-i18next imports them for Trans; they were importable only because every declaration in the type files counts as exported.

fix(types): with nsSeparator: false in CustomTypeOptions, the key union no longer contains nsfalsekey-style keys for the other namespaces, and a key that contains the text false (isfalsey) is no longer split at it, which typed its t() result as never.

fix: with clones (i18next-http-middleware makes one per request), saveMissing now checks that the namespace is loaded for the instance that misses the key. Each cloneInstance() pointed the parent's services.utils.hasLoadedNamespace at the new clone, and the backend connector, which all clones share, used that one: a key missing in one request was not saved (did not save key ... as the namespace ... was not yet loaded) while a newer request was still loading its language, and the parent's services.utils answered for the newest clone. A clone's services.utils is now bound to the clone, and the parent keeps its own. A direct services.backendConnector.saveMissing() call, like the missing keys route of i18next-http-middleware, still checks the newest clone (follow-up to #1413).

fix: dir() without a language (before init(), or with no language resolved) returns 'ltr' instead of 'rtl' ([discussion #2135](https://github.com/i18next/i18next/discussions/2135)).

fix: t() before init() returns an empty string, as typed (with a warning when debug logging is already on); it returned undefined.

fix: off('a b', listener) removes the listener from both events, as on('a b', listener) adds it to both. It looked for an event named 'a b', so once('a b', listener) never removed its listener and ran it on every event.

deprecate: dotted languages in the resource store calls (getResource('en.translation.key'), addResource('en.translation.key', value), addResourceBundle('en.translation', resources)) log a deprecation warning in debug mode; they are removed in v27. Pass language, namespace and key as separate arguments.

deprecate: interpolation.prefixEscaped, suffixEscaped, nestingPrefixEscaped and nestingSuffixEscaped (inserted into the RegExp unescaped) log a deprecation warning in debug mode and are marked @deprecated; they are removed in v27. Pass the literal delimiters as prefix, suffix, nestingPrefix and nestingSuffix.

deprecate: compatibilityJSON is marked @deprecated (it has no effect since v24) and removed from the types in v27.

deprecate: a language code without a region that v27 canonicalizes differently logs a deprecation warning in debug mode: 'EN' stays 'EN' today and becomes 'en' in v27, 'iw' becomes 'he'. cleanCode: true already lower-cases them.

deprecate: when fallbackLng is not set, the first request for the default fallback language dev (loading it, or saving missing keys to it) logs a notice in debug mode: v27 defaults to fallbackLng: false and no longer requests dev. Set fallbackLng to your source language, or to 'dev' to keep the current behavior.

deprecate: in debug mode, a language code that comes from lng, changeLanguage() or the language detector, is not configured (supportedLngs, fallbackLng, preload or the resources) and fails isSafeLanguageCode logs a deprecation warning, once per code: without supportedLngs, a detector that returns "><img src=x onerror=alert(1)> makes that string i18next.language, and apps put it into <html lang>. Nothing changes in 26.7; v27 is planned to refuse such codes and continue as with an unsupported code. Language codes are still not bound to a format.

deprecate: the logger and post-processors are shared by all instances in v26 and per instance from v27 (clones keep their parent's). In debug mode, an instance that runs a post-processor only another instance registered with use() logs a deprecation warning (call use() on this instance too), and a non-clone init() that replaces the logger another instance set with use() logs one through that logger.

deprecate: in debug mode, a value with a / under the default escape logs that v27 no longer escapes / ($10/month renders as $10/month today; not with escapeValue: false, where react-i18next's Trans escapes one call itself and decodes the entities afterwards), and an object or array hit without returnObjects logs that v27 returns the key instead of the sentence key '... (en)' returned an object instead of string..

... (truncated)

Changelog

Sourced from i18next's changelog.

26.7.1

fix: reloadResources() retries the bundles that failed to load. The load queue skipped them also when reloading, so a language whose first load failed (a backend or network outage at startup) stayed missing. i18next-http-backend 4.0.8, i18next-chained-backend 5.0.7 and i18next-locize-backend 10.0.5 reload through reloadResources() with i18next 26.7, so their reloadInterval no longer recovered from such a failure, as their own reload did before.

fix: reloadResources() without languages reloads the current languages and every language the backend loaded or tried to load, for the instance and its clones, as the API docs describe ("pass languages and namespaces if you don't want to reload all"). It reloaded only the current languages, so on a server (one clone per request with i18next-http-middleware) a backend's reloadInterval never refreshed the languages loaded for requests. It never requests cimode. With languages given, nothing changes.

26.7.0

The last 26.x minor before v27, which follows in about a week. It adds the APIs v27 builds on, and with debug: true it warns wherever a setup relies on something v27 changes. Most of the v27 defaults are existing options, so you can try them now:
i18next.init({
 debug: true, // prints the warnings below
 fallbackLng: 'en', // v27: fallbackLng defaults to false, set your source language (no implicit 'dev')
 returnEmptyString: false, // v27 default: an empty string falls back like a missing key
 cleanCode: true, // close to v27, which canonicalizes codes without a region ('EN' becomes 'en')
});
declare module 'i18next' {
 interface CustomTypeOptions {
 strictInterpolationChecks: true; // v27 default
 returnEmptyString: false; // v27 default
 }
}
The other v27 changes (/ no longer escaped in values, a logger and post-processors per instance, the key instead of a sentence for an object hit, the dotted-language store calls and *Escaped options removed) have no switch; the debug warnings below show where they apply.

feat: with the default skipOnVariables: true, a missing interpolation variable is now logged in debug mode, once per string and variable: missed to pass in variable name for interpolating Hello {{name}}. The raw {{name}} reached the UI without any log line, even with debug: true, because the warning only ran with skipOnVariables: false. A variable passed as undefined and a missingInterpolationHandler still log nothing.

feat: i18next.hydrate(resources, lng) puts resources rendered on the server into the store and changes to the server's language, each only the first time. It does what react-i18next's useSSR did by writing resourceStore.data, options.ns, isInitialized, initializedStoreOnce and initializedLanguageOnce directly, and sets the same flags, so integrations can switch to it and stay compatible with code that still reads or writes them. On a clone it does nothing, as useSSR does: a clone shares its parent's store (one clone per request with i18next-http-middleware). Called before init(), it logs a warning and changes nothing.

feat: services.utils.reloadResources() lets a backend reload its bundles through i18next (as i18next.reloadResources(), with retries and the loaded event), instead of calling backendConnector.read() and loaded() itself as the reloadInterval of i18next-http-backend and i18next-chained-backend does. Without languages (no lng, no detector, the default fallbackLng), reloadResources() reloads nothing instead of throwing Cannot read properties of undefined (reading 'forEach'); a backend that also reloads preload passes its languages.

feat: backends and async language detectors can declare their calling convention with callbackApi (an instance or static property). true: read(language, namespace, callback), create(languages, namespace, key, fallbackValue, callback, options) and detect(callback); false: they return a promise or a value, and create gets the options as its fifth argument. Without it, i18next keeps guessing from the number of parameters (Function.length), which default and rest parameters change: i18next-chained-backend's create(..., clb = () => {}, opts = {}) has length 4 and never got its options (isUpdate), and i18next-http-backend's callback form of create has length 5, the length reserved for the callback-less form. Guessing is deprecated: in debug mode an unmarked backend or async detector logs a deprecation warning, once per init().

feat: isSafeLanguageCode(code) is exported for plugins that take a language from a request, a URL or storage: letters, digits, -, _, @ and . (no ..), at most 128 characters, not a prototype key. It is not a BCP 47 check, so en_US, zh_Hant_TW, sr@latin and de_DE.UTF-8 pass; markup, slashes and spaces do not. The language detector, i18next-http-middleware and i18next-http-backend each have their own rule today.

feat: use() logs a warning in debug mode when a second backend, language detector, i18nFormat or formatter replaces the first one; only one of each is used per instance, and losing an ICU setup this way was silent. As use() usually runs before init(), the warning is printed once init() has set up the logger.

feat(types): ParseKeysWithoutVariables<Ns, KPrefix>, the keys t() takes without options: their string has no variables, and a plural key is left out when its forms take count. A wrapper typed with it, like (key: ParseKeysWithoutVariables<'common'>) => t(key), compiles with strictInterpolationChecks without a cast.

feat(types): defaultVariables in CustomTypeOptions declares the variables interpolation.defaultVariables fills in at runtime (defaultVariables: { appName: string }). They become optional in the t() options, also with strictInterpolationChecks; passed, they keep their type.

feat(types): interpolationFormatSeparator in CustomTypeOptions for a custom interpolation.formatSeparator: the types split {{price, currency}} at a hard-coded ,, so with formatSeparator: ';' the format was not recognized. The per-call skipInterpolation option is typed, and returnedObjectHandler may return a value (what it returns is what t() returns; it was typed as returning void).

feat(types): SelectorFn, ApplyTarget, ConstrainTarget and GetSource are exported on purpose, under their current names. react-i18next imports them for Trans; they were importable only because every declaration in the type files counts as exported.

fix(types): with nsSeparator: false in CustomTypeOptions, the key union no longer contains nsfalsekey-style keys for the other namespaces, and a key that contains the text false (isfalsey) is no longer split at it, which typed its t() result as never.

fix: with clones (i18next-http-middleware makes one per request), saveMissing now checks that the namespace is loaded for the instance that misses the key. Each cloneInstance() pointed the parent's services.utils.hasLoadedNamespace at the new clone, and the backend connector, which all clones share, used that one: a key missing in one request was not saved (did not save key ... as the namespace ... was not yet loaded) while a newer request was still loading its language, and the parent's services.utils answered for the newest clone. A clone's services.utils is now bound to the clone, and the parent keeps its own. A direct services.backendConnector.saveMissing() call, like the missing keys route of i18next-http-middleware, still checks the newest clone (follow-up to #1413).

fix: dir() without a language (before init(), or with no language resolved) returns 'ltr' instead of 'rtl' ([discussion #2135](https://github.com/i18next/i18next/discussions/2135)).

fix: t() before init() returns an empty string, as typed (with a warning when debug logging is already on); it returned undefined.

fix: off('a b', listener) removes the listener from both events, as on('a b', listener) adds it to both. It looked for an event named 'a b', so once('a b', listener) never removed its listener and ran it on every event.

deprecate: dotted languages in the resource store calls (getResource('en.translation.key'), addResource('en.translation.key', value), addResourceBundle('en.translation', resources)) log a deprecation warning in debug mode; they are removed in v27. Pass language, namespace and key as separate arguments.

deprecate: interpolation.prefixEscaped, suffixEscaped, nestingPrefixEscaped and nestingSuffixEscaped (inserted into the RegExp unescaped) log a deprecation warning in debug mode and are marked @deprecated; they are removed in v27. Pass the literal delimiters as prefix, suffix, nestingPrefix and nestingSuffix.

deprecate: compatibilityJSON is marked @deprecated (it has no effect since v24) and removed from the types in v27.

deprecate: a language code without a region that v27 canonicalizes differently logs a deprecation warning in debug mode: 'EN' stays 'EN' today and becomes 'en' in v27, 'iw' becomes 'he'. cleanCode: true already lower-cases them.

deprecate: when fallbackLng is not set, the first request for the default fallback language dev (loading it, or saving missing keys to it) logs a notice in debug mode: v27 defaults to fallbackLng: false and no longer requests dev. Set fallbackLng to your source language, or to 'dev' to keep the current behavior.

deprecate: in debug mode, a language code that comes from lng, changeLanguage() or the language detector, is not configured (supportedLngs, fallbackLng, preload or the resources) and fails isSafeLanguageCode logs a deprecation warning, once per code: without supportedLngs, a detector that returns "><img src=x onerror=alert(1)> makes that string i18next.language, and apps put it into <html lang>. Nothing changes in 26.7; v27 is planned to refuse such codes and continue as with an unsupported code. Language codes are still not bound to a format.

... (truncated)

Commits

b84e418 26.7.1
0a9fc2e changelog for 26.7.1
61fae7e fix: reloadResources() retries bundles that failed and, without languages, re...
70b64a2 26.7.0
f98d0c6 changelog for 26.7.0
8e37fb2 ci: type check the public types on TypeScript 5.0, the lowest of the peer range
c976112 feat: hydrate() and services.utils.reloadResources for SSR integrations and b...
9f426b2 feat: debug warnings for a missing interpolation variable, a module replaced ...
1dbb93a fix: with clones, saveMissing checks the namespaces of the instance that miss...
3bfbe2e feat(types): ParseKeysWithoutVariables and defaultVariables for strictInterpo...
Additional commits viewable in compare view

Updates `lucide-react` from 1.61.0 to 1.66.0

Release notes

Sourced from lucide-react's releases.

Version 1.66.0

What's Changed

feat(icons): added monitor-activity icon by @karsa-mistmere in lucide-icons/lucide#5090

chore(deps): bump the github-actions group across 1 directory with 4 updates by @dependabot[bot] in lucide-icons/lucide#5111

feat(icons): added file-database icon by @PrimeTestLab in lucide-icons/lucide#5014

feat(icons): added margin-bottom, margin-horizontal, margin-left and 11 more icons by @irvineacosta in lucide-icons/lucide#3525

feat(groups): added chart and graph groups by @karsa-mistmere in lucide-icons/lucide#5124

feat(site): Add Hover And Focus Animations Across The Docs Site by @PrimeTestLab in lucide-icons/lucide#5085

feat(icons): added chart-bell-curve icon by @karsa-mistmere in lucide-icons/lucide#5128

fix(icons): update design of *-letter-p-off icons to match new base icon designs by @karsa-mistmere in lucide-icons/lucide#5129

Full Changelog: https://github.com/lucide-icons/lucide/compare/1.65.0...1.66.0

Version 1.65.0

What's Changed

chore(deps): Update deps astro package by @ericfennis in lucide-icons/lucide#5108

ci(claude-review): Turn off claude review by @ericfennis in lucide-icons/lucide#5109

chore(deps): bump rollup to 4.65.1 and keep typescript on v6 by @dependabot[bot] in lucide-icons/lucide#5110

chore(deps): bump nuxt from 4.5.1 to 4.6.2 by @dependabot[bot] in lucide-icons/lucide#5068

ci(claude-review|repo-journal): Remove workflows by @ericfennis in lucide-icons/lucide#5118

chore(deps-dev): bump the testing-deps group across 1 directory with 4 updates by @dependabot[bot] in lucide-icons/lucide#5116

feat(metadata|docs|site): reuse metadata from a base icon with $extends: by @ericfennis in lucide-icons/lucide#4360

feat(metadata|docs): reusable tag groups with $group: by @ericfennis in lucide-icons/lucide#5037

feat(metadata): apply tag groups to variant icons by @ericfennis in lucide-icons/lucide#5038

chore(metadata): apply more tag groups to icon variants by @karsa-mistmere in lucide-icons/lucide#5093

chore(metadata): Clean up icon categories by @ericfennis in lucide-icons/lucide#5099

fix(icons): removed letters-digits category from anything that wasn't one by @karsa-mistmere in lucide-icons/lucide#5104

feat(groups): added letter & digit groups by @karsa-mistmere in lucide-icons/lucide#5105

ci(suggest-metadata): Add support for $extends and $group in metadata suggestions by @ericfennis in lucide-icons/lucide#5117

chore(deps-dev): bump the preact-deps group across 1 directory with 2 updates by @dependabot[bot] in lucide-icons/lucide#5115

chore(deps-dev): bump react-native-svg from 15.15.5 to 15.16.0 in the react-native-deps group by @dependabot[bot] in lucide-icons/lucide#5113

fix(astro): support stricter optional property checking by @latin-1 in lucide-icons/lucide#5070

New Contributors

@latin-1 made their first contribution in lucide-icons/lucide#5070

Full Changelog: https://github.com/lucide-icons/lucide/compare/1.64.0...1.65.0

Version 1.64.0

What's Changed

chore(docs|site): Remove Plausible, add tracking events and privacy statement by @ericfennis in lucide-icons/lucide#5092

feat(icons): added square-kanban-plus icon by @KesleyDavid in lucide-icons/lucide#4688

feat(icons): added letter-b, letter-c, letter-d and 21 more icons by @karsa-mistmere in lucide-icons/lucide#4743

feat(icons): added numbers icon by @karsa-mistmere in lucide-icons/lucide#4778

feat(icons): added circle-letter-a, circle-letter-b, circle-letter-c and 46 more icons by @karsa-mistmere in lucide-icons/lucide#4744

feat(icons): added new Letters & digits category by @karsa-mistmere in lucide-icons/lucide#5095

fix(icons): align Unicode currency icon cap heights with other typographic icons by @karsa-mistmere in lucide-icons/lucide#4926

ci(claude-review): add Claude PR review workflow by @ericfennis in lucide-icons/lucide#5097

fix(icons): remove bracket from square-letter-d.svg by @ericfennis in lucide-icons/lucide#5101

... (truncated)

Commits

1668a0c chore(deps): bump rollup to 4.65.1 and keep typescript on v6 (#5110)
e8f86fc fix(lucide-react): ignore stale DynamicIcon loads after the name changes (#5060)
6657faa chore(deps-dev): bump vite from 8.3.2 to 8.3.3 (#5052)
1802f33 feat(lucide-react): add package exports for per-icon imports without changing...
20aef31 chore(packages): Update sponsors (#5034)
See full diff in compare view

Updates `react-i18next` from 17.1.9 to 17.1.13

Changelog

Sourced from react-i18next's changelog.

17.1.13

fix(types): the react init options keep their types with i18next 27. i18next 27 declares ReactOptions (the type of i18next.init({ react })) as an empty interface and leaves its shape to react-i18next, so with react-i18next 17 the react options were no longer checked and getDefaults().useSuspense did not compile. react-i18next now declares them itself, with exactly the types i18next 26 has: TypeScript accepts the repeated declaration on i18next 26, and on i18next 27 it fills in the empty interface. Nothing changes with i18next 26.

17.1.12

fix(types): type-checking a <Trans> is fast again with large resources. Since 17.0.2 the return type of the key was a type parameter of Trans, so TypeScript also computed it for every key of the namespace: with 50 namespaces of 200 keys, one <Trans> cost about 1.3 million more type instantiations than in 17.0.1, with or without a values prop. The return type is computed inside the values prop again, as in 17.0.1, and values still only needs the variables of the given i18nKey (#1913). The exported TransProps type loses the Ret parameter added in 17.0.2, so its 6th parameter is the element props E again, as before 17.0.2. Thanks @leshaduduk (#1947), fixes #1946.

17.1.11

fix(Trans): with i18next 26.7.0 or later and debug: true, the variables of object children are no longer logged as missing. When Trans interpolates before parsing (with count, values, tOptions or interpolation.defaultVariables), its t() call leaves the placeholders of object children like {{ name }} for after parsing, and i18next 26.7 logs each of them as missed to pass in variable name, although the output is right: <Trans count={n}>Hello {{ name }}, you have {{ count }} messages.</Trans> logged it for name. Trans now passes a missingInterpolationHandler to that call that does what i18next does without one (it keeps the placeholder, and a variable passed as undefined becomes empty), so the output is unchanged. It does not with skipOnVariables: false, a missingInterpolationHandler of your own, an i18nFormat plugin, or an escape function that would change the placeholders of the children.

17.1.10

fix(Trans): markup inside an interpolated value is no longer parsed as translation markup. Trans interpolates values (and count, values in tOptions, or the whole string when there are no children) before it parses the string. With interpolation.escapeValue: false, or with an i18nFormat plugin (i18next-icu, i18next-mf2, i18next-fluent), which inserts values without escaping whatever escapeValue says, a value like <0 href="https://example.com">x</0> was rendered as component 0 with that href, overriding the props of the component, and x in a value became a real . Trans now escapes the values for this t() call (with a plugin, the string values in values) and decodes the entities after parsing, so such a value renders as text, and a " in a value no longer closes an attribute like <Item title="{{name}}" />. {{- var}} stays the explicit way for a translator to insert a value unescaped. As with shouldUnescape, entities written in these translations (for example &) are now decoded instead of shown literally. Output with escapeValue: true and no plugin, with i18next-icu escapeVariables: true, and with children and no values or count is unchanged.

fix(IcuTrans): the same for IcuTrans with escapeValue: false or an i18nFormat plugin: a value like <0>x</0> no longer becomes the first component, and a value containing an entity like & is no longer decoded a second time.

Commits

76c1842 17.1.13
4dd03fe changelog for 17.1.13
2d792a4 fix(types): the react init options keep their types with i18next 27
a6b635d chore: update dependencies and examples, close the dependabot alerts
cbac86f README: drop the Locize ad image; the sponsor banner and the text saying who ...
95ab2f3 17.1.12
91cfa41 changelog for 17.1.12
a98b743 fix(types): compute the Trans values type inside the prop again (#1947)
541e248 17.1.11
31325a1 build
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-automerge-start) [//]: # (dependabot-automerge-end) ---

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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions

dev / openkara

chore(deps): bump the production-dependencies group with 4 updates