build(deps): bump the production-dependencies group across 1 directory with 13 updates

[dependabot]

Bumps the production-dependencies group with 13 updates in the / directory:

Package	From	To
@react-navigation/bottom-tabs	7.18.14	7.18.18
@react-navigation/native	7.3.14	7.3.18
@react-navigation/native-stack	7.18.6	7.18.10
i18next	26.3.6	26.4.2
pretty-bytes	7.1.1	7.1.3
react-i18next	17.0.11	17.0.13
react-native-paper-dates	0.23.15	0.23.16
react-native-reanimated	4.5.3	4.6.0
react-native-safe-area-context	5.8.0	5.9.1
react-native-screens	4.26.2	4.27.0
react-native-toast-message	2.4.0	2.5.0
react-native-worklets	0.11.3	0.12.1
styled-components	6.4.4	6.5.3

Updates @react-navigation/bottom-tabs from 7.18.14 to 7.18.18

Release notes

Sourced from @​react-navigation/bottom-tabs's releases.

@​react-navigation/bottom-tabs@​7.18.17

7.18.17 (2026-08-19)

Bug Fixes

• read latest state to determine pop to top (1a29cb4) - by @​satya164

Changelog

Sourced from @​react-navigation/bottom-tabs's changelog.

7.18.18 (2026-08-26)

Note: Version bump only for package @​react-navigation/bottom-tabs

7.18.17 (2026-08-19)

Bug Fixes

• read latest state to determine pop to top (1a29cb4) - by @​satya164

7.18.16 (2026-08-07)

Note: Version bump only for package @​react-navigation/bottom-tabs

7.18.15 (2026-08-05)

Note: Version bump only for package @​react-navigation/bottom-tabs

Commits

• 5555d32 chore: publish
• 900d2c4 chore: publish
• 1a29cb4 fix: read latest state to determine pop to top
• 749aaf5 chore: publish
• 680d889 chore: publish
• See full diff in compare view

Updates @react-navigation/native from 7.3.14 to 7.3.18

Release notes

Sourced from @​react-navigation/native's releases.

@​react-navigation/native@​7.3.18

7.3.18 (2026-08-26)

Bug Fixes

• prevent state reset when history.go() takes longer than timeout on web (#13217) (1b309a7) - by @​collectioneur

@​react-navigation/native@​7.3.17

7.3.17 (2026-08-19)

Bug Fixes

• ensure linking actions are handled by root navigator (e00a3ac) - by @​satya164
• fix return type of getRootState (4e6eaaa) - by @​satya164
• update useScrollToTop type so SectionList ref works under RN 0.87 strict types (#13221) (6dc33e7) - by @​ErfanBagheri404

@​react-navigation/native@​7.3.15

7.3.15 (2026-08-05)

Bug Fixes

• workaround VSCode autoimport not working for useNavigation etc (1d26955), closes #13204 - by @

Changelog

Sourced from @​react-navigation/native's changelog.

7.3.18 (2026-08-26)

Bug Fixes

• prevent state reset when history.go() takes longer than timeout on web (#13217) (1b309a7) - by @​collectioneur

7.3.17 (2026-08-19)

Bug Fixes

• ensure linking actions are handled by root navigator (e00a3ac) - by @​satya164
• fix return type of getRootState (4e6eaaa) - by @​satya164
• update useScrollToTop type so SectionList ref works under RN 0.87 strict types (#13221) (6dc33e7) - by @​ErfanBagheri404

7.3.16 (2026-08-07)

Note: Version bump only for package @​react-navigation/native

7.3.15 (2026-08-05)

Bug Fixes

• workaround VSCode autoimport not working for useNavigation etc (1d26955), closes #13204 - by @

Commits

• 5555d32 chore: publish
• 1b309a7 fix: prevent state reset when history.go() takes longer than timeout on web (...
• 900d2c4 chore: publish
• 6dc33e7 fix: update useScrollToTop type so SectionList ref works under RN 0.87 strict...
• e00a3ac fix: ensure linking actions are handled by root navigator
• 4e6eaaa fix: fix return type of getRootState
• 749aaf5 chore: publish
• 680d889 chore: publish
• 1d26955 fix: workaround VSCode autoimport not working for useNavigation etc
• See full diff in compare view

Updates @react-navigation/native-stack from 7.18.6 to 7.18.10

Release notes

Sourced from @​react-navigation/native-stack's releases.

@​react-navigation/native-stack@​7.18.9

7.18.9 (2026-08-19)

Bug Fixes

• read latest state to determine pop to top (1a29cb4) - by @​satya164

Changelog

Sourced from @​react-navigation/native-stack's changelog.

7.18.10 (2026-08-26)

Note: Version bump only for package @​react-navigation/native-stack

7.18.9 (2026-08-19)

Bug Fixes

• read latest state to determine pop to top (1a29cb4) - by @​satya164

7.18.8 (2026-08-07)

Note: Version bump only for package @​react-navigation/native-stack

7.18.7 (2026-08-05)

Note: Version bump only for package @​react-navigation/native-stack

Commits

• 5555d32 chore: publish
• c68ce9e chore: make wanrings and errors fail the tests
• 900d2c4 chore: publish
• 1a29cb4 fix: read latest state to determine pop to top
• 749aaf5 chore: publish
• 680d889 chore: publish
• See full diff in compare view

Updates i18next from 26.3.6 to 26.4.2

Release notes

Sourced from i18next's releases.

v26.4.2

• fix: $&, $`, $' and $$ inside a nested value ($t(key)) now stay literal. nest() handed the resolved value straight to String.replace as the replacement argument, so those sequences were read as replacement patterns: $& re-inserted the $t(...) match, $` / $' inserted the text before / after it, and $$ collapsed to $. Through t() the $& case was worse than a wrong string: the nested lookup resets the shared nesting regexp, so the re-inserted $t(...) was matched again on every pass and t() never returned — also under the default escapeValue: true when the value arrives via a variable forwarded through nesting options ($t(key, { "name": "{{name}}" }) with a name containing $&). The value is now $-escaped at the String.replace call, the same guard interpolate() already has, and a non-string value returned by a formatter in the nesting chain ($t(key, myFormat)) is stringified before that. Nested values are still not HTML-escaped (#854). Thanks @​mahirhir (#2447).

v26.4.1

• fix(types): the selector-form keyPrefix overload of getFixedT() is now available under enableSelector: 'strict'. Its constraint was gated on true | 'optimize' only, so under 'strict' it collapsed to never, the overload dropped out, and the returned t silently lost its keyPrefix scope (t(($) => $.deep) failed with Property 'deep' does not exist on type '{}'). The same call already typechecked under true and 'optimize'. Thanks @​hovelopin (#2446).

v26.4.0

• perf: cache toResolveHierarchy results per (code, fallbackCode) pair. The hierarchy resolver runs on every t() call and calls Intl.getCanonicalLocales multiple times, which showed up prominently when profiling render-heavy UIs (e.g. virtualized data grids); with the cache the per-call cost drops from ~886 ns to ~41 ns. The cache is invalidated automatically when options.fallbackLng changes (reassignment or in-place array mutation); if you mutate other resolution-relevant options at runtime (load, lowerCaseLng, cleanCode, nonExplicitSupportedLngs), call i18next.services.languageUtils.clearCache() afterwards. Function-valued fallbackLng and per-call array/object fallbackLng options are never cached, so dynamic fallbacks keep working as before. Thanks @​equaterina (#2444).
• chore: update all devDependencies (Babel stays on 7.x until @rollup/plugin-babel supports 8, eslint on 9.x for neostandard). Removed the unused coveralls package (CI uses the Coveralls GitHub Action) and replaced sinon with nise + vitest.spyOn in the v1 compatibility tests, which resolves all open npm audit findings (0 vulnerabilities) and should close the dependabot alerts on the lockfile.

Changelog

Sourced from i18next's changelog.

26.4.2

• fix: $&, $`, $' and $$ inside a nested value ($t(key)) now stay literal. nest() handed the resolved value straight to String.replace as the replacement argument, so those sequences were read as replacement patterns: $& re-inserted the $t(...) match, $` / $' inserted the text before / after it, and $$ collapsed to $. Through t() the $& case was worse than a wrong string: the nested lookup resets the shared nesting regexp, so the re-inserted $t(...) was matched again on every pass and t() never returned — also under the default escapeValue: true when the value arrives via a variable forwarded through nesting options ($t(key, { "name": "{{name}}" }) with a name containing $&). The value is now $-escaped at the String.replace call, the same guard interpolate() already has, and a non-string value returned by a formatter in the nesting chain ($t(key, myFormat)) is stringified before that. Nested values are still not HTML-escaped (#854). Thanks @​mahirhir (#2447).

26.4.1

• fix(types): the selector-form keyPrefix overload of getFixedT() is now available under enableSelector: 'strict'. Its constraint was gated on true | 'optimize' only, so under 'strict' it collapsed to never, the overload dropped out, and the returned t silently lost its keyPrefix scope (t(($) => $.deep) failed with Property 'deep' does not exist on type '{}'). The same call already typechecked under true and 'optimize'. Thanks @​hovelopin (#2446).

26.4.0

• perf: cache toResolveHierarchy results per (code, fallbackCode) pair. The hierarchy resolver runs on every t() call and calls Intl.getCanonicalLocales multiple times, which showed up prominently when profiling render-heavy UIs (e.g. virtualized data grids); with the cache the per-call cost drops from ~886 ns to ~41 ns. The cache is invalidated automatically when options.fallbackLng changes (reassignment or in-place array mutation); if you mutate other resolution-relevant options at runtime (load, lowerCaseLng, cleanCode, nonExplicitSupportedLngs), call i18next.services.languageUtils.clearCache() afterwards. Function-valued fallbackLng and per-call array/object fallbackLng options are never cached, so dynamic fallbacks keep working as before. Thanks @​equaterina (#2444).
• chore: update all devDependencies (Babel stays on 7.x until @rollup/plugin-babel supports 8, eslint on 9.x for neostandard). Removed the unused coveralls package (CI uses the Coveralls GitHub Action) and replaced sinon with nise + vitest.spyOn in the v1 compatibility tests, which resolves all open npm audit findings (0 vulnerabilities) and should close the dependabot alerts on the lockfile.

Commits

• 4dba50f 26.4.2
• e436b62 build
• d955fb0 fix: stringify formatter results in nested values, changelog v26.4.2
• dfafa3c fix: keep replacement patterns literal in nested values (#2447)
• 3c9981e chore: keep dev-only and local files out of the npm package
• c057ee0 26.4.1
• 02e3e16 changelog v26.4.1
• 6f198f2 fix(types): allow selector keyPrefix in getFixedT under enableSelector 'stric...
• 652847e 26.4.0
• 6c6025f prettier fix
• Additional commits viewable in compare view

Updates pretty-bytes from 7.1.1 to 7.1.3

Release notes

Sourced from pretty-bytes's releases.

v7.1.3

• Fix fractional digit formatting when localization is disabled (#92) 5cb9c95

---

sindresorhus/pretty-bytes@v7.1.2...v7.1.3

v7.1.2

• Fix rounding across unit boundaries 059c979

---

sindresorhus/pretty-bytes@v7.1.1...v7.1.2

Commits

• 4fc8ed9 7.1.3
• ef9e45c Improve non-localized fractional digit coverage
• 5cb9c95 Fix fractional digit formatting when localization is disabled (#92)
• deb9a2c 7.1.2
• 059c979 Fix rounding across unit boundaries
• See full diff in compare view

Updates react-i18next from 17.0.11 to 17.0.13

Changelog

Sourced from react-i18next's changelog.

17.0.13

• fix(types): the selector-form keyPrefix overload of useTranslation() is now available under enableSelector: 'strict'. useTranslation was gated on true | 'optimize' only, so under 'strict' it resolved to the legacy signature and the selector overload disappeared entirely (keyPrefix: ($) => $.ns.foo failed with Type '($: any) => any' is not assignable to type 'undefined'). Trans already handled all three modes. Companion to the same fix for getFixedT in i18next#2446. Thanks @​hovelopin (#1930).

17.0.12

• fix(IcuTrans): key-less icu.macro nodes (<Trans>Welcome, {name}!</Trans>, <Select>, <Plural> without i18nKey) rendered an empty string since 17.0.0. The macro now emits <IcuTrans defaultTranslation="…"> without a key and IcuTrans passed undefined to t(), which returns ''. Like Trans, IcuTrans now uses defaultTranslation as the key when i18nKey is not provided.

Commits

• addf646 17.0.13
• 7c634ee changelog v17.0.13
• 5ceefb0 fix(types): allow selector keyPrefix in useTranslation under enableSelector '...
• aa7ba52 chore(examples): require activesupport >= 7.2.3.1 in the RN Gemfiles
• ec0bb4e chore(examples): drop react_native_windows and the RN Gemfile.locks
• aa5fc43 build
• ea721fb 17.0.12
• 6c2a71e fix(IcuTrans): use defaultTranslation as key when no i18nKey is given
• 258c96d chore(examples): upgrade all example apps off unmaintained toolchains
• b8677c8 chore: update dependencies to close dependabot alerts
• Additional commits viewable in compare view

Updates react-native-paper-dates from 0.23.15 to 0.23.16

Release notes

Sourced from react-native-paper-dates's releases.

Release 0.23.16

What's Changed

• Align date picker modal corner radius with MD3 extra-large by @​iM-GeeKy in web-ridge/react-native-paper-dates#540

Full Changelog: web-ridge/react-native-paper-dates@v0.23.15...v0.23.16

Commits

• 7801fdb chore: release 0.23.16
• e8dfbb9 Align date picker modal corner radius with MD3 extra-large (#540)
• See full diff in compare view

Updates react-native-reanimated from 4.5.3 to 4.6.0

Release notes

Sourced from react-native-reanimated's releases.

Reanimated - 4.6.0

Key changes

React Native 0.87 support

Reanimated 4.6 supports React Native 0.83 – 0.87 and pairs with Worklets 0.12.x. See the compatibility table.

• fix(Reanimated): background_image prop for RN 0.87 by @​tjzel in software-mansion/react-native-reanimated#9768
• chore: upgrade React Native to 0.87.0 by @​pawicao in software-mansion/react-native-reanimated#10236

CSS animation and transition callbacks on native

onCSSAnimationStart, onCSSAnimationEnd, onCSSAnimationIteration, onCSSAnimationCancel, onCSSTransitionRun, onCSSTransitionStart, onCSSTransitionEnd and onCSSTransitionCancel now fire on iOS and Android.

• feat: web support for CSS animation callbacks by @​MatiPl01 in software-mansion/react-native-reanimated#9605
• feat: report CSS animation events from the engine by @​MatiPl01 in software-mansion/react-native-reanimated#10070
• feat: CSS animation callbacks on native by @​MatiPl01 in software-mansion/react-native-reanimated#10071
• feat: batch CSS events and deliver them to JS by @​MatiPl01 in software-mansion/react-native-reanimated#10108
• feat: deliver batched CSS events to JS by @​MatiPl01 in software-mansion/react-native-reanimated#10107
• feat: report CSS transition events from the engine by @​MatiPl01 in software-mansion/react-native-reanimated#10119
• feat: CSS transition callbacks on native by @​MatiPl01 in software-mansion/react-native-reanimated#10124
• feat: report the lifecycle milestones a transition crosses by @​MatiPl01 in software-mansion/react-native-reanimated#10271
• chore: prefix the CSS lifecycle callbacks with onCSS by @​MatiPl01 in software-mansion/react-native-reanimated#10273
• feat: take the CSS lifecycle callbacks as props by @​MatiPl01 in software-mansion/react-native-reanimated#10252
• fix: deliver the CSS animation cancel emitted while a view unmounts by @​MatiPl01 in software-mansion/react-native-reanimated#10255

contrastColor utility

New contrastColor worklet, a port of CSS contrast-color(). It returns 'white' or 'black', whichever has the higher WCAG contrast ratio against the given color. It works inside useAnimatedStyle and other worklets as well as on the JS thread. See the docs.

• feat: add contrastColor function by @​tomekzaw in software-mansion/react-native-reanimated#10320

Experimental: platform-driven CSS transitions on Android

opacity CSS transitions can now run on the Android platform with ObjectAnimator, off the animation loop. This is the Android counterpart of iOS Core Animation transitions.

The feature is off by default. Enable it with the ANDROID_CSS_PLATFORM_TRANSITIONS feature flag.

• feat: Add the Android animator for CSS platform transitions by @​MatiPl01 in software-mansion/react-native-reanimated#10090
• feat: Keep platform-driven CSS transition values alive across React Native writes by @​MatiPl01 in software-mansion/react-native-reanimated#10092
• feat: Resolve CSS transition timelines for Android and bridge them over JNI by @​MatiPl01 in software-mansion/react-native-reanimated#10060
• feat: Route opacity CSS transitions to the Android platform path by @​MatiPl01 in software-mansion/react-native-reanimated#10240
• fix: Play CSS transition delays inside the animation by @​MatiPl01 in software-mansion/react-native-reanimated#10242
• fix: Drop Android CSS transition animators when the React context goes by @​MatiPl01 in software-mansion/react-native-reanimated#10241
• perf: Intern easings and route properties by id across the transition JNI by @​MatiPl01 in software-mansion/react-native-reanimated#10269
• perf: Batch transition commands into one main-looper message by @​MatiPl01 in software-mansion/react-native-reanimated#10213
• perf: Retry pending transition starts from one shared frame callback by @​MatiPl01 in software-mansion/react-native-reanimated#10214
• fix: run transitions with callbacks on the loop instead of the platform by @​MatiPl01 in software-mansion/react-native-reanimated#10228
• fix: Prime platform transitions before the first frame draws by @​MatiPl01 in software-mansion/react-native-reanimated#10326
• docs: document the feature flags for platform-routed CSS transitions by @​MatiPl01 in software-mansion/react-native-reanimated#10328

... (truncated)

Commits

• 8651062 release(Reanimated): 4.6.0 (#10366)
• a874ac1 chore: prepare branch for reanimated 4.6.0 release (#10363)
• 8d5e8ff fix(Reanimated): read the window size from the base revision when the LA prox...
• 885cdab fix: reject non-finite CSS durations and delays (#10360)
• 2fcaac4 fix: keep the reversing shortening factor within [0, 1] (#10359)
• 02403d4 fix: return a finite value when linear() control points share an input prog...
• f41b838 fix: correct the control points of the predefined ease easing function (#10...
• 1f0b70e fix: correct the cubic-bezier x-derivative used to solve CSS easings (#10344)
• d1f72fb [Docs] Update sponsors section (#10347)
• 74350d5 fix: Text losing its trailing word after a CSS fontSize transition on Android...
• Additional commits viewable in compare view

Updates react-native-safe-area-context from 5.8.0 to 5.9.1

Release notes

Sourced from react-native-safe-area-context's releases.

Release 5.9.1

5.9.1 (2026-08-18)

Bug Fixes

• register src/paper/java as a Java source set on old architecture (#755) (780f599), closes #733 #754

Release 5.9.0

5.9.0 (2026-08-12)

Bug Fixes

• avoid NotFoundError when the measurement element is already detached (#746) (76dfb06)
• make nested SafeAreaProvider report its own frame and insets on web (#737) (2fa707d)
• update insets and frame on window resize on web (#736) (1fe7ec5)

Features

• Adopt AGP v9 (#733) (42c50a6)

Release 5.8.1

5.8.1 (2026-08-03)

Bug Fixes

• Move jest/mock into package build (fix TS under RN 0.87) (#745) (b9e2857)
• skip Fabric SafeAreaView state updates while detached from window (#735) (ae0e83f)

Features

• upgrade to react-native 0.85.0 with RNTA 5.3.2 (#732) (4d00f52)

Commits

• 63fab20 chore: release 5.9.1
• 780f599 fix: register src/paper/java as a Java source set on old architecture (#755)
• f65d4d9 chore: release 5.9.0
• 76dfb06 fix: avoid NotFoundError when the measurement element is already detached (#746)
• 2fa707d fix: make nested SafeAreaProvider report its own frame and insets on web (#737)
• 1fe7ec5 fix: update insets and frame on window resize on web (#736)
• 42c50a6 feat: Adopt AGP v9 (#733)
• b3cfc57 chore: release 5.8.1
• 2f7f2e9 rm tea.yaml
• b9e2857 fix: Move jest/mock into package build (fix TS under RN 0.87) (#745)
• Additional commits viewable in compare view

Updates react-native-screens from 4.26.2 to 4.27.0

Release notes

Sourced from react-native-screens's releases.

4.27.0

What's changed

This release adds support for React Native 0.87, fixing a runtime crash on iOS in the process. It also introduces the experimental ScrollToTopGuard component and fully migrates the Split component implementation from Swift to Objective-C.

✅ Improvements

• feat(Android, Stack v5): support sending multiple updates via view command (#4243)
• refactor(test): Add scenario for Stack v5 preventNativeDismiss with nested stack (#4279)
• feat(Stack v5, iOS): Implement basic view commands for iOS header menu (#4339)
• feat(experimental, iOS): add experimental ScrollToTopGuard component (#4454)
• refactor: change default value of backTitleVisible to true instead of 'true' (#4457)
• chore(iOS, Split): Migrate ReactMountingTransactionObserving to obj-c (#4458)
• chore(iOS, Split): Migrate Appearance-related logic to obj-c (#4459)
• chore: add support for react-native@0.87.0-rc.3 (#4461)
• chore(iOS, Split): Migrate RNSSplitNavigationController to obj-c (#4462)
• chore(iOS, Split): Migrate RNSSplitScreenController to obj-c (#4463)
• chore(iOS, Split): Migrate RNSSplitHostController to Obj-C with all associated classes (#4465)
• chore(iOS): Post Swift-removal cleanup (#4466)
• feat(ios, Stack v4): add subtitle support for UIMenu header button submenus (#4469)

🐞 Bugfixes

• fix(Android): defensively guard against an unexpected menuItem Id (#4450)
• fix(Android, Stack): don't add top inset to measured header height when it's disabled (#4452)
• fix(iOS, Stack v4): fall back to inheriting orientation if it's not defined on the screen (#4455)
• fix(iOS): Don't swap view controller's view during transition (#4456)
• fix(iOS, Tabs): re-layout tab bar after async icon load to prevent label truncation on iOS 26 (#4460)
• fix(Android): Fix crash when header gets update during screen removal (#4468)
• fix(Android, FormSheet v4): Cleanup inset and layout listener (#4470)
• fix(JS): Prevent using ViewInstance type (#4471)
• fix(iOS, Stack v5): use framework-style imports for React core headers (#4472)

Misc

• chore(examples): allow explicit undefined for defaultRouteName in TabsContainerStateInitArg (#4353)
• chore: block the possibility to create plain-text issues and update agents instructions (#4366)
• chore: Update workflows to include v4-main (#4396)
• chore: Remove nightly publishing flows from v4 and bump npm-package-publish (#4401)
• chore: bump react-navigation submodule version (#4451)
• chore: format RNSScreenShadowNode.cpp after #4357 (#4453)
• chore(Android): Fix incremental compilation in FabricExample broken by Kotlin 2.2 symlink issue (#4467)

Commits

• 42c1615 release: 4.27.0 (#4475)
• 2b55ed6 fix(iOS): Add missing RNSScrollToTopGuard stubs (#4480)
• 1ce9142 Revert "chore: backport #4411 (#4460)" (#4477)
• 973def6 chore: backport #4402 (#4472)
• d59af14 chore: backport #4447 (#4471)
• 23ba913 chore: backport #4449 (#4470)
• 9aa7d2a chore: backport #4107 (#4469)
• 2ac61a1 chore: backport #4444 (#4468)
• c993a72 chore: backport #4443 (#4467)
• 85f7a08 chore: backport #4426 (#4466)
• Additional commits viewable in compare view

Updates react-native-toast-message from 2.4.0 to 2.5.0

Release notes

Sourced from react-native-toast-message's releases.

v2.5.0

What's Changed

• fix(web): avoid deprecated shadow props by @​huytdps13400 in calintamas/react-native-toast-message#601
• fix(web): reset terminated toast pans by @​huytdps13400 in calintamas/react-native-toast-message#602
• fix(web): avoid useLayoutEffect during SSR by @​huytdps13400 in calintamas/react-native-toast-message#603
• feat: support custom BaseToast test IDs by @​huytdps13400 in calintamas/react-native-toast-message#604
• feat: expose visibilityTime to custom layouts by @​huytdps13400 in calintamas/react-native-toast-message#605
• chore(deps): bump js-yaml from 3.14.1 to 3.15.1 by @​dependabot[bot] in calintamas/react-native-toast-message#599
• chore(deps): bump brace-expansion from 1.1.11 to 1.1.16 by @​dependabot[bot] in calintamas/react-native-toast-message#598

New Contributors

• @​huytdps13400 made their first contribution in calintamas/react-native-toast-message#601

Full Changelog: calintamas/react-native-toast-message@v2.4.0...v2.5.0

Commits

• 0a3d37f build: release v2.5.0
• Description has been truncated