Skip to content

chore(deps): bump the compatible-updates group with 12 updates - #380

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/compatible-updates-97188bf611
Open

chore(deps): bump the compatible-updates group with 12 updates#380
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/compatible-updates-97188bf611

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 2, 2026

Copy link
Copy Markdown
Contributor

Bumps the compatible-updates group with 12 updates:

Package From To
@tauri-apps/plugin-deep-link 2.6.2 2.6.3
@tauri-apps/plugin-dialog 2.8.3 2.8.4
@tauri-apps/plugin-updater 2.14.0 2.14.1
framer-motion 14.6.0 14.8.0
hls.js 1.7.3 1.7.4
i18next 26.5.6 26.5.11
lucide-react 1.61.0 1.64.0
react-i18next 17.1.3 17.1.9
react-router-dom 7.18.4 7.18.5
virtua 0.53.6 0.54.0
autoprefixer 10.6.1 10.6.2
postcss 8.5.31 8.5.32

Updates @tauri-apps/plugin-deep-link from 2.6.2 to 2.6.3

Release notes

Sourced from @​tauri-apps/plugin-deep-link's releases.

deep-link-js v2.6.3

[2.6.3]

  • c92bb67d (#3382 by @​Amjad50) The iOS associated domains entitlement is no longer overwritten on build: the plugin now only replaces its applinks: entries and keeps the other entries your app adds, such as webcredentials: for passkeys.

  • 8dc878fe (#3383 by @​mvanhorn) On Linux, register and unregister no longer fail when update-desktop-database is not installed. A warning is logged and the MIME cache update is skipped.

  • 46397767 (#3711 by @​FabianLars) Fixed a compilation error with rust-ini v0.21.3.

  • c92bb67d (#3382 by @​Amjad50) Fixed the iOS CFBundleURLTypes generation: every configured custom URL scheme is now registered, including schemes listed next to https/http in the same mobile entry, and web link entries no longer produce an empty URL type.

    The generated iOS CFBundleURLName is now $(PRODUCT_BUNDLE_IDENTIFIER).{scheme}.

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-deep-link@2.6.3
npm notice Tarball Contents
npm notice 888B LICENSE.spdx
npm notice 6.5kB README.md
npm notice 4.7kB dist-js/index.cjs
npm notice 4.0kB dist-js/index.d.ts
npm notice 4.6kB dist-js/index.js
npm notice 801B package.json
npm notice Tarball Details
npm notice name: @tauri-apps/plugin-deep-link
npm notice version: 2.6.3
npm notice filename: tauri-apps-plugin-deep-link-2.6.3.tgz
npm notice package size: 4.9 kB
npm notice unpacked size: 21.5 kB
npm notice shasum: d7f47990f0247ab6c09636a0a274251ced224e6b
npm notice integrity: sha512-L+fjyGe5RPBtf[...]7VyiecBBdiy/A==
npm notice total files: 6
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=3529332341
npm notice Your package is being processed and may take a few minutes to become available.
+ @tauri-apps/plugin-deep-link@2.6.3

deep-link v2.6.3

[2.6.3]

... (truncated)

Commits
  • 1281906 publish new versions (#3712)
  • 52fa775 chore(deps): update rust crate rand to 0.10 (#3738)
  • 1331ca4 chore(deps): update rust crate rfd to 0.17 (#3737)
  • 385f60c chore(deps): update rust crate base64 to 0.23 (#3515)
  • 8e04d30 chore(deps): update dependency @​tauri-apps/cli to v2.12.4 (#3717)
  • 34ed7d3 chore(deps): update dependency @​rollup/plugin-terser to v1.0.2 (#3733)
  • c75459d chore(deps): update dependency rollup to v4.64.12 (#3715)
  • df59420 chore(deps): update webpki-roots crates (lockfile-only) (#3723)
  • 11211c3 fix(window-state): stop macOS overlay windows changing size on every restore ...
  • f36ba7b feat(notification): add Android chronometer support (#3282)
  • Additional commits viewable in compare view

Updates @tauri-apps/plugin-dialog from 2.8.3 to 2.8.4

Release notes

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

dialog-js v2.8.4

[2.8.4]

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-dialog@2.8.4
npm notice Tarball Contents
npm notice 888B LICENSE.spdx
npm notice 3.5kB README.md
npm notice 7.1kB dist-js/index.cjs
npm notice 15.1kB dist-js/index.d.ts
npm notice 7.0kB dist-js/index.js
npm notice 11B dist-js/init.d.ts
npm notice 657B package.json
npm notice Tarball Details
npm notice name: @tauri-apps/plugin-dialog
npm notice version: 2.8.4
npm notice filename: tauri-apps-plugin-dialog-2.8.4.tgz
npm notice package size: 6.8 kB
npm notice unpacked size: 34.3 kB
npm notice shasum: 994ee0f6a1a440a1b9f47bd7b03886d082b76c41
npm notice integrity: sha512-+6ZOiXenOaxXw[...]kWGej4a7dC4lw==
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=3529333044
npm notice Your package is being processed and may take a few minutes to become available.
+ @tauri-apps/plugin-dialog@2.8.4

dialog v2.8.4

[2.8.4]

... (truncated)

Commits
  • 1281906 publish new versions (#3712)
  • 52fa775 chore(deps): update rust crate rand to 0.10 (#3738)
  • 1331ca4 chore(deps): update rust crate rfd to 0.17 (#3737)
  • 385f60c chore(deps): update rust crate base64 to 0.23 (#3515)
  • 8e04d30 chore(deps): update dependency @​tauri-apps/cli to v2.12.4 (#3717)
  • 34ed7d3 chore(deps): update dependency @​rollup/plugin-terser to v1.0.2 (#3733)
  • c75459d chore(deps): update dependency rollup to v4.64.12 (#3715)
  • df59420 chore(deps): update webpki-roots crates (lockfile-only) (#3723)
  • 11211c3 fix(window-state): stop macOS overlay windows changing size on every restore ...
  • f36ba7b feat(notification): add Android chronometer support (#3282)
  • Additional commits viewable in compare view

Updates @tauri-apps/plugin-updater from 2.14.0 to 2.14.1

Release notes

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

updater-js v2.14.1

[2.14.1]

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-updater@2.14.1
npm notice Tarball Contents
npm notice 888B LICENSE.spdx
npm notice 3.2kB README.md
npm notice 6.9kB dist-js/index.cjs
npm notice 7.1kB dist-js/index.d.ts
npm notice 6.8kB dist-js/index.js
npm notice 659B package.json
npm notice Tarball Details
npm notice name: @tauri-apps/plugin-updater
npm notice version: 2.14.1
npm notice filename: tauri-apps-plugin-updater-2.14.1.tgz
npm notice package size: 4.9 kB
npm notice unpacked size: 25.5 kB
npm notice shasum: f1ae182e36409a7d32cdfbfc897b1c848b7ff94d
npm notice integrity: sha512-Hr7nlBm1wT6xb[...]35UqnbrQxmYQw==
npm notice total files: 6
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=3529335775
npm notice Your package is being processed and may take a few minutes to become available.
+ @tauri-apps/plugin-updater@2.14.1

updater v2.14.1

[2.14.1]

... (truncated)

Commits
  • 1281906 publish new versions (#3712)
  • 52fa775 chore(deps): update rust crate rand to 0.10 (#3738)
  • 1331ca4 chore(deps): update rust crate rfd to 0.17 (#3737)
  • 385f60c chore(deps): update rust crate base64 to 0.23 (#3515)
  • 8e04d30 chore(deps): update dependency @​tauri-apps/cli to v2.12.4 (#3717)
  • 34ed7d3 chore(deps): update dependency @​rollup/plugin-terser to v1.0.2 (#3733)
  • c75459d chore(deps): update dependency rollup to v4.64.12 (#3715)
  • df59420 chore(deps): update webpki-roots crates (lockfile-only) (#3723)
  • 11211c3 fix(window-state): stop macOS overlay windows changing size on every restore ...
  • f36ba7b feat(notification): add Android chronometer support (#3282)
  • Additional commits viewable in compare view

Updates framer-motion from 14.6.0 to 14.8.0

Changelog

Sourced from framer-motion's changelog.

[14.8.0] 2026-10-29

Added

  • transition: Added mixer option for passing custom mixer functions.

Fixed

  • Only counts projection stats while recordStats() is running.
  • Fix accelerated animations stuck at initial after remount.
  • drag: 20% smaller.
  • m component: 6% smaller.
  • Keep timeline adjustments within timeline scope.
  • Reorder

[14.7.1] 2026-10-27

Fixed

  • Demote transforms to CPU when interrupted by layout animations.

[14.7.0] 2026-10-27

Added

  • animate: Mutable timeline sequences.
  • animate: Relative label offsets for timeline sequences.
  • useScroll: Returns scrollXLength and scrollYLength.
  • Reorder: Add LazyMotion-compatible import.
  • motion: transition.out prop for transitions when exiting a state.

Fixed

  • Fix one flash when changing playback speed of accelerated independent transform.
  • AnimatePresence: Improved positioning of popped elements.
  • spring: Fix overdamped springs snapping to target.
  • drag: Ref-constraints kept up-to-date after scroll.
  • motion: Animate layoutId elements relative to layoutRoot container.
  • motion: Bundle size reductions.
  • Moving background-color animations back to main thread for improved interpolation.
  • drag: Fix drag inertia stopping dead after a fast flick from a standstill.
  • layout: layoutId elements now animate relative to their closest layoutRoot ancestor, if any.
  • layout: layoutId may be changed after mount.
  • useScroll: Fix tracking in horizontal containers.
  • useSpring: Reduced bundle size by 30%.
Commits
  • 1b27a83 v14.8.0
  • 4d29f83 Poll in timing-dependent Playwright assertions
  • 161f75c Updating changelog
  • 2bc460c Merge pull request #4017 from motiondivision/claude/project-thread-45aghj-tra...
  • 02f87ff Merge pull request #4025 from motiondivision/claude/project-thread-vr1k3n
  • 233f96b Merge pull request #4024 from motiondivision/claude/project-thread-k8ixr1
  • f3b4700 Merge branch 'main' into claude/project-thread-k8ixr1
  • 18c18bd Merge pull request #4014 from motiondivision/claude/project-thread-45aghj-van...
  • 9bf12d5 Merge the remote branch, which merged main without #4013
  • cd3e233 Merge main into claude/project-thread-45aghj-vanilla-drag-node
  • Additional commits viewable in compare view

Updates hls.js from 1.7.3 to 1.7.4

Release notes

Sourced from hls.js's releases.

v1.7.4

Summary

HLS.js v1.7.4 includes bug fixes and improvements over the last release.

Changes Since The Last Release

video-dev/hls.js@v1.7.3...v1.7.4

Bug fixes and improvements

Low-latency HLS

  • Fix skipping unloaded trailing parts at fragment boundaries (#8055) @​darfink
  • Advance part loading once all parts of a fragment are loaded (#8134, follow-up to #8055) @​robwalch
  • Adjust playlist position using first part start PTS (#8105, fixes #8098)
  • Fix repeated audio buffer flushing when setting nextAudioTrack during Low-Latency HLS part loading (#8104)
  • Fix LL-HLS subtitle stall from one-ULP rounding in final-part comparison (#8057, fixes #8051) @​akashchamp

Content protection (DRM / EME)

  • Reuse attached MediaKeys across loadSource (#8095, fixes #8092) @​krseager
  • Reuse attached MediaKeys when loadSource re-attaches media, and serialize setMediaKeys calls (#8120, fixes #8092) @​matvp91
    • Introduces experimental, opt-in only, reuseKeySessions configuration option
  • Keep pending setMediaKeys when the same keys are requested while media is detached (#8076)
  • FairPlay Streaming: reset MediaKeys when changing the MediaSource (#8131) @​robwalch

Interstitials

  • Set a schedule position when interstitial fallback happens with nothing playing (#8088) @​Arthur031221
  • Trigger INTERSTITIAL_ENDED for unresolved interstitials (empty asset-list, or removed from schedule while loading) (#8090, fixes #8082) @​robwalch

Alternate audio

  • Prevent loop loading of audio in the next discontinuity (f86f24724) @​robwalch
  • Complete audio track switch when switching back to the currently playing track (#8093, fixes #8089) @​krseager
  • Defer main BUFFER_EOS while an alternate audio track switch is in progress (#8053) @​brandonocasey

Subtitles & captions (WebVTT / IMSC1)

Fragment loading & stream controllers

... (truncated)

Commits
  • 142fcab Merge pull request #8135 from video-dev/renovate/chromedriver-155.x
  • 9a4da62 Update dependency chromedriver to v155
  • a95c27d Advance part loading once all parts of a fragment are loaded
  • f86f247 Prevent loop loading of audio in next discontinuity
  • cf349a4 Mark fragments as gaps on SourceBuffer errors (#8045)
  • d8a64e7 Merge pull request #8132 from video-dev/renovate/wrangler-4.x
  • cdfb89c Update dependency wrangler to v4.151.3
  • f52a523 Don't keep MediaKeys with FairPlay Streaming
  • 8647fa2 Reuse attached MediaKeys when loadSource re-attaches media and serialize setM...
  • e0afa07 Merge pull request #8130 from video-dev/renovate/wrangler-4.x
  • Additional commits viewable in compare view

Updates i18next from 26.5.6 to 26.5.11

Release notes

Sourced from i18next's releases.

v26.5.11

  • fix: a nested false, 0 or '' is now returned when a flat key with the same dotted name also exists. With { a: { b: false }, 'a.b': 'flat' }, getResource('en', 'translation', 'a.b') and t('a.b') returned 'flat': the nested result was checked for truthiness, so these present values fell through to the flat-key lookup. Without such a flat key they were already returned. A nested null, which is not a valid lookup by default (returnNull: false), still falls back to the flat key. Thanks @​lprnmns (#2461).

v26.5.10

  • fix: when none of the detected languages is in supportedLngs, the best match no longer picks a different language whose code only starts with the same letters. The last fuzzy check took any supported code starting with the language part, so with supportedLngs: ['en', 'fil-PH'] a Finnish user (fi-FI) got Filipino instead of the fallback language, and ha (Hausa) picked haw-US (Hawaiian). Other regions of the same language still match as before (de-CH → de-DE, pt-PT → pt-BR, fil → fil-PH). Compatibility note: a two-letter code no longer matches a supported three-letter code that extends it, like ar → arz-EG, sw → swh-KE or no → nob-NO; list the two-letter code in supportedLngs (or map it with fallbackLng) if you relied on that. Thanks @​Pharex38 (#2460).

v26.5.9

  • fix: nested lookups no longer resolve to methods inherited from the prototype, like constructor, toString or map. Only the top level was guarded, so {{constructor}} was treated as missing, but {{user.constructor}} rendered the function source (with a class instance, the full source code of the class), and {{user.toString}}, {{items.map}} or a class method like {{user.greet}} did the same. The same lookup is used for translation keys when ignoreJSONStructure is on (the default): a nested key named like an inherited method that is missing in the current language (t('roles.constructor') with roles.constructor only in the fallback language) returned function Object() { [native code] } instead of falling back, and exists('roles.valueOf') returned true. These keys are now missing, so the fallback language, missingInterpolationHandler, saveMissing and the missing key handler apply as for any other missing key. Getters defined on a class ({{user.fullName}} with get fullName()) still work. Nested lookups also no longer walk into the prototype via __proto__, so {{user.__proto__.constructor}} no longer prints the class source either. Thanks @​Pharex38 (#2459).

v26.5.8

  • fix: arrays returned with joinArrays now get the same resolved details as strings. The joined value was extended with lastKey in the place of the resolved lookup, so with postProcessPassResolved a post processor got no usedLng, usedNS or exactUsedKey (t('steps', { joinArrays: ' / ' }) reported undefined/undefined:undefined). This affected the subliminal post processor used by the locize InContext editor, which could not map a joined array to its key. The nesting recursion guard did not get the parent key either, so arrays that nest each other (listA: ['a', '$t(listB)'], listB: ['b', '$t(listA)']) threw Maximum call stack size exceeded. They now stop at the guard, as strings do. An i18nFormat plugin with handleAsObject and parse also no longer throws Cannot read properties of undefined (reading 'usedNS') on joined arrays. Thanks @​nk-batman21 (#2458).

v26.5.7

  • fix: with the default cacheInBuiltFormats: true, built-in formats now also work when the t() options contain a BigInt or a circular object. The cache key was built with JSON.stringify over all options, including the interpolation values, which throws on those, so every built-in format in that call returned the raw value: t('num', { val: 12345678901234567890n }) with 'Total: {{val, number}}' returned 'Total: 12345678901234567890' instead of 'Total: 12,345,678,901,234,567,890', and passing an object with a back-reference (like an ORM entity) left all numbers, dates and lists of that call unformatted. When the key cannot be built, the value is now formatted without the cache, as with cacheInBuiltFormats: false. This also applies to formatters added with addCached. Other calls still use the cache as before. Thanks @​nk-batman21 (#2457).
Changelog

Sourced from i18next's changelog.

26.5.11

  • fix: a nested false, 0 or '' is now returned when a flat key with the same dotted name also exists. With { a: { b: false }, 'a.b': 'flat' }, getResource('en', 'translation', 'a.b') and t('a.b') returned 'flat': the nested result was checked for truthiness, so these present values fell through to the flat-key lookup. Without such a flat key they were already returned. A nested null, which is not a valid lookup by default (returnNull: false), still falls back to the flat key. Thanks @​lprnmns (#2461).

26.5.10

  • fix: when none of the detected languages is in supportedLngs, the best match no longer picks a different language whose code only starts with the same letters. The last fuzzy check took any supported code starting with the language part, so with supportedLngs: ['en', 'fil-PH'] a Finnish user (fi-FI) got Filipino instead of the fallback language, and ha (Hausa) picked haw-US (Hawaiian). Other regions of the same language still match as before (de-CH → de-DE, pt-PT → pt-BR, fil → fil-PH). Compatibility note: a two-letter code no longer matches a supported three-letter code that extends it, like ar → arz-EG, sw → swh-KE or no → nob-NO; list the two-letter code in supportedLngs (or map it with fallbackLng) if you relied on that. Thanks @​Pharex38 (#2460).

26.5.9

  • fix: nested lookups no longer resolve to methods inherited from the prototype, like constructor, toString or map. Only the top level was guarded, so {{constructor}} was treated as missing, but {{user.constructor}} rendered the function source (with a class instance, the full source code of the class), and {{user.toString}}, {{items.map}} or a class method like {{user.greet}} did the same. The same lookup is used for translation keys when ignoreJSONStructure is on (the default): a nested key named like an inherited method that is missing in the current language (t('roles.constructor') with roles.constructor only in the fallback language) returned function Object() { [native code] } instead of falling back, and exists('roles.valueOf') returned true. These keys are now missing, so the fallback language, missingInterpolationHandler, saveMissing and the missing key handler apply as for any other missing key. Getters defined on a class ({{user.fullName}} with get fullName()) still work. Nested lookups also no longer walk into the prototype via __proto__, so {{user.__proto__.constructor}} no longer prints the class source either. Thanks @​Pharex38 (#2459).

26.5.8

  • fix: arrays returned with joinArrays now get the same resolved details as strings. The joined value was extended with lastKey in the place of the resolved lookup, so with postProcessPassResolved a post processor got no usedLng, usedNS or exactUsedKey (t('steps', { joinArrays: ' / ' }) reported undefined/undefined:undefined). This affected the subliminal post processor used by the locize InContext editor, which could not map a joined array to its key. The nesting recursion guard did not get the parent key either, so arrays that nest each other (listA: ['a', '$t(listB)'], listB: ['b', '$t(listA)']) threw Maximum call stack size exceeded. They now stop at the guard, as strings do. An i18nFormat plugin with handleAsObject and parse also no longer throws Cannot read properties of undefined (reading 'usedNS') on joined arrays. Thanks @​nk-batman21 (#2458).

26.5.7

  • fix: with the default cacheInBuiltFormats: true, built-in formats now also work when the t() options contain a BigInt or a circular object. The cache key was built with JSON.stringify over all options, including the interpolation values, which throws on those, so every built-in format in that call returned the raw value: t('num', { val: 12345678901234567890n }) with 'Total: {{val, number}}' returned 'Total: 12345678901234567890' instead of 'Total: 12,345,678,901,234,567,890', and passing an object with a back-reference (like an ORM entity) left all numbers, dates and lists of that call unformatted. When the key cannot be built, the value is now formatted without the cache, as with cacheInBuiltFormats: false. This also applies to formatters added with addCached. Other calls still use the cache as before. Thanks @​nk-batman21 (#2457).
Commits

Updates lucide-react from 1.61.0 to 1.64.0

Release notes

Sourced from lucide-react's releases.

Version 1.64.0

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@1.63.0...1.64.0

Version 1.63.0

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@1.62.0...1.63.0

Version 1.62.0

What's Changed

... (truncated)

Commits
  • 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.3 to 17.1.9

Changelog

Sourced from react-i18next's changelog.

17.1.9

  • fix(useTranslation): namespaces added to or removed from the ns array are now picked up. The hook used the array itself as the useMemo dependency list, and React only compares the entries both lists have in common when its length changes, so going from useTranslation(['nsA']) to useTranslation(['nsA', 'nsB']) kept returning ['nsA']: React warned that the dependency array changed size, nsB was never loaded, and with nsMode: 'fallback' keys only in nsB rendered as the key. Removing a namespace kept the old list the same way. The namespaces are now compared by content, so a growing list loads the new namespace (suspending until it is loaded, as switching from 'nsA' to 'nsB' already does) and t uses it. Lists that keep their length behave as before. Thanks @​lprnmns (#1945).

17.1.8

  • fix(Trans): an interpolation variable named format is no longer dropped. Trans reads format in an interpolation object as the formatter name ({{ value, format }}), so with {{ format }} as the only key nothing was left: <Trans>Export as {{ format }}</Trans> warned TRANS_INVALID_OBJ and used the default string Export as instead of Export as {{format}}. When format is the object's only key it is now treated as the variable. {{ value, format }} works as before. Without an i18nKey, the key derived from the children changes accordingly, from Export as to Export as {{format}}. i18next-cli serializes Trans children with react-i18next, so extracting with this version produces the same key. Thanks @​Pharex38 (#1944).

17.1.7

  • fix(IcuTrans): each HTML entity in a translation is now decoded exactly once. Named, decimal and hexadecimal entities were decoded in three passes, and each pass decoded the output of the previous one, so an escaped numeric entity was decoded twice: "Write &amp;[#169](https://github.com/i18next/react-i18next/issues/169); to get &[#169](https://github.com/i18next/react-i18next/issues/169);" rendered Write © to get © instead of Write &[#169](https://github.com/i18next/react-i18next/issues/169); to get ©, and &amp;[#60](https://github.com/i18next/react-i18next/issues/60); rendered < instead of &[#60](https://github.com/i18next/react-i18next/issues/60);. This also hit interpolated values with escapeValue: true, where a value containing &[#60](https://github.com/i18next/react-i18next/issues/60); is escaped to &amp;[#60](https://github.com/i18next/react-i18next/issues/60);. Escaped named entities like &amp;lt; already stayed &lt;, as browsers and Trans decode them. Unknown named entities and entities above U+10FFFF still stay as written. Thanks @​Pharex38 (#1943).

17.1.6

  • fix(Trans): a count passed in tOptions is now used. Trans spread tOptions and then set its own count prop, so a count only in tOptions was overwritten with undefined: <Trans i18nKey="items" tOptions={{ count: 5 }} /> rendered the key items instead of 5 items, and with children Trans could pick the wrong plural form. Like context, Trans now falls back to tOptions.count, handled the same way as the count prop. A count prop, a count in the children or values.count still take precedence, and tOptions is not modified. Thanks @​nk-batman21 (#1942).

17.1.5

  • fix(Trans): with an array of keys and no children, Trans now falls back to the last key when none of them has a translation, as t() does. It used the array itself as defaultValue, which i18next handles as an object, so <Trans i18nKey={['notifications.crm_item_created', 'crm_item_created']} components={[<strong />]} /&...

    Description has been truncated

@dependabot
chore(deps): bump the compatible-updates group with 12 updates
4c5941a 
Bumps the compatible-updates group with 12 updates:

| Package | From | To |
| --- | --- | --- |
| [@tauri-apps/plugin-deep-link](https://github.com/tauri-apps/plugins-workspace) | `2.6.2` | `2.6.3` |
| [@tauri-apps/plugin-dialog](https://github.com/tauri-apps/plugins-workspace) | `2.8.3` | `2.8.4` |
| [@tauri-apps/plugin-updater](https://github.com/tauri-apps/plugins-workspace) | `2.14.0` | `2.14.1` |
| [framer-motion](https://github.com/motiondivision/motion) | `14.6.0` | `14.8.0` |
| [hls.js](https://github.com/video-dev/hls.js) | `1.7.3` | `1.7.4` |
| [i18next](https://github.com/i18next/i18next) | `26.5.6` | `26.5.11` |
| [lucide-react](https://github.com/lucide-icons/lucide/tree/HEAD/packages/lucide-react) | `1.61.0` | `1.64.0` |
| [react-i18next](https://github.com/i18next/react-i18next) | `17.1.3` | `17.1.9` |
| [react-router-dom](https://github.com/remix-run/react-router/tree/HEAD/packages/react-router-dom) | `7.18.4` | `7.18.5` |
| [virtua](https://github.com/inokawa/virtua) | `0.53.6` | `0.54.0` |
| [autoprefixer](https://github.com/postcss/autoprefixer) | `10.6.1` | `10.6.2` |
| [postcss](https://github.com/postcss/postcss) | `8.5.31` | `8.5.32` |


Updates `@tauri-apps/plugin-deep-link` from 2.6.2 to 2.6.3
- [Release notes](https://github.com/tauri-apps/plugins-workspace/releases)
- [Commits](tauri-apps/plugins-workspace@deep-link-v2.6.2...deep-link-v2.6.3)

Updates `@tauri-apps/plugin-dialog` from 2.8.3 to 2.8.4
- [Release notes](https://github.com/tauri-apps/plugins-workspace/releases)
- [Commits](tauri-apps/plugins-workspace@http-v2.8.3...dialog-v2.8.4)

Updates `@tauri-apps/plugin-updater` from 2.14.0 to 2.14.1
- [Release notes](https://github.com/tauri-apps/plugins-workspace/releases)
- [Commits](tauri-apps/plugins-workspace@updater-v2.14.0...updater-v2.14.1)

Updates `framer-motion` from 14.6.0 to 14.8.0
- [Changelog](https://github.com/motiondivision/motion/blob/main/CHANGELOG.md)
- [Commits](motiondivision/motion@v14.6.0...v14.8.0)

Updates `hls.js` from 1.7.3 to 1.7.4
- [Release notes](https://github.com/video-dev/hls.js/releases)
- [Changelog](https://github.com/video-dev/hls.js/blob/master/docs/release-process.md)
- [Commits](video-dev/hls.js@v1.7.3...v1.7.4)

Updates `i18next` from 26.5.6 to 26.5.11
- [Release notes](https://github.com/i18next/i18next/releases)
- [Changelog](https://github.com/i18next/i18next/blob/master/CHANGELOG.md)
- [Commits](i18next/i18next@v26.5.6...v26.5.11)

Updates `lucide-react` from 1.61.0 to 1.64.0
- [Release notes](https://github.com/lucide-icons/lucide/releases)
- [Commits](https://github.com/lucide-icons/lucide/commits/1.64.0/packages/lucide-react)

Updates `react-i18next` from 17.1.3 to 17.1.9
- [Changelog](https://github.com/i18next/react-i18next/blob/master/CHANGELOG.md)
- [Commits](i18next/react-i18next@v17.1.3...v17.1.9)

Updates `react-router-dom` from 7.18.4 to 7.18.5
- [Release notes](https://github.com/remix-run/react-router/releases)
- [Changelog](https://github.com/remix-run/react-router/blob/react-router-dom@7.18.5/packages/react-router-dom/CHANGELOG.md)
- [Commits](https://github.com/remix-run/react-router/commits/react-router-dom@7.18.5/packages/react-router-dom)

Updates `virtua` from 0.53.6 to 0.54.0
- [Release notes](https://github.com/inokawa/virtua/releases)
- [Commits](inokawa/virtua@0.53.6...0.54.0)

Updates `autoprefixer` from 10.6.1 to 10.6.2
- [Release notes](https://github.com/postcss/autoprefixer/releases)
- [Changelog](https://github.com/postcss/autoprefixer/blob/main/CHANGELOG.md)
- [Commits](postcss/autoprefixer@10.6.1...10.6.2)

Updates `postcss` from 8.5.31 to 8.5.32
- [Release notes](https://github.com/postcss/postcss/releases)
- [Changelog](https://github.com/postcss/postcss/blob/main/CHANGELOG.md)
- [Commits](postcss/postcss@8.5.31...8.5.32)

---
updated-dependencies:
- dependency-name: "@tauri-apps/plugin-deep-link"
  dependency-version: 2.6.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: compatible-updates
- dependency-name: "@tauri-apps/plugin-dialog"
  dependency-version: 2.8.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: compatible-updates
- dependency-name: "@tauri-apps/plugin-updater"
  dependency-version: 2.14.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: compatible-updates
- dependency-name: framer-motion
  dependency-version: 14.8.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: compatible-updates
- dependency-name: hls.js
  dependency-version: 1.7.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: compatible-updates
- dependency-name: i18next
  dependency-version: 26.5.11
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: compatible-updates
- dependency-name: lucide-react
  dependency-version: 1.64.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: compatible-updates
- dependency-name: react-i18next
  dependency-version: 17.1.9
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: compatible-updates
- dependency-name: react-router-dom
  dependency-version: 7.18.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: compatible-updates
- dependency-name: virtua
  dependency-version: 0.54.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: compatible-updates
- dependency-name: autoprefixer
  dependency-version: 10.6.2
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: compatible-updates
- dependency-name: postcss
  dependency-version: 8.5.32
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: compatible-updates
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants