Bump the production-dependencies group across 1 directory with 17 updates

[dependabot]

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

Package	From	To
@react-navigation/bottom-tabs	7.15.11	7.16.2
@react-navigation/native	7.2.2	7.2.5
@react-navigation/native-stack	7.14.12	7.16.0
@reduxjs/toolkit	2.11.2	2.12.0
fuse.js	7.3.0	7.4.0
i18next	26.0.8	26.3.0
react-i18next	17.0.6	17.0.8
react-native-charts-wrapper	0.6.0	0.7.0
react-native-paper	5.15.1	5.15.3
react-native-paper-dates	0.23.6	0.23.9
react-native-reanimated	4.3.0	4.4.0
react-native-safe-area-context	5.7.0	5.8.0
react-native-screens	4.24.0	4.25.2
react-native-svg	15.15.4	15.15.5
react-native-worklets	0.8.3	0.9.1
react-redux	9.2.0	9.3.0
styled-components	6.4.1	6.4.2

Updates @react-navigation/bottom-tabs from 7.15.11 to 7.16.2

Release notes

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

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

7.16.2 (2026-05-25)

Bug Fixes

• default lazy to true for native tabs to avoid flicker (ca4ac56) - by @​satya164

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

7.16.0 (2026-05-11)

Bug Fixes

• default multiselectable to undefined (cd466d4) - by @​satya164

Features

• add ability to prevent tab bar selection (1930fa0) - by @​satya164
• update native tabs to use the new API in react-native-screens (a12db96) - by @​satya164

Changelog

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

7.16.2 (2026-05-25)

Bug Fixes

• default lazy to true for native tabs to avoid flicker (ca4ac56) - by @​satya164

7.16.1 (2026-05-14)

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

7.16.0 (2026-05-11)

Bug Fixes

• default multiselectable to undefined (cd466d4) - by @​satya164

Features

• add ability to prevent tab bar selection (1930fa0) - by @​satya164
• update native tabs to use the new API in react-native-screens (a12db96) - by @​satya164

7.15.13 (2026-05-08)

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

7.15.12 (2026-05-07)

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

Commits

• b89bba2 chore: publish
• ca4ac56 fix: default lazy to true for native tabs to avoid flicker
• 8e0ce2b chore: publish
• b5b1f7c chore: publish
• cd466d4 fix: default multiselectable to undefined
• 1930fa0 feat: add ability to prevent tab bar selection
• a12db96 feat: update native tabs to use the new API in react-native-screens
• 01ae31e chore: publish
• e8a05bb chore: publish
• 1a9623c refactor: backport API changes from 8.x and add deprecations
• See full diff in compare view

Updates @react-navigation/native from 7.2.2 to 7.2.5

Release notes

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

@​react-navigation/native@​7.2.4

7.2.4 (2026-05-08)

Bug Fixes

• fix linking prefix matching host with additional characters (680a3eb) - by @​satya164
• fix URLs with hashes not being matched correctly (5a884b1) - by @​satya164
• handle errors in parsing query params gracefully (ec42524) - by @​satya164

Changelog

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

7.2.5 (2026-05-25)

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

7.2.4 (2026-05-08)

Bug Fixes

• fix linking prefix matching host with additional characters (680a3eb) - by @​satya164
• fix URLs with hashes not being matched correctly (5a884b1) - by @​satya164
• handle errors in parsing query params gracefully (ec42524) - by @​satya164

7.2.3 (2026-05-07)

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

Commits

• b89bba2 chore: publish
• 01ae31e chore: publish
• 680a3eb fix: fix linking prefix matching host with additional characters
• ec42524 fix: handle errors in parsing query params gracefully
• 5a884b1 fix: fix URLs with hashes not being matched correctly
• e8a05bb chore: publish
• d43e3c2 refactor: support module augmentation for default types
• fae561d refactor: dispatch back instead of reset if we determine it's a simple pop (#...
• See full diff in compare view

Updates @react-navigation/native-stack from 7.14.12 to 7.16.0

Release notes

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

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

7.16.0 (2026-05-25)

Features

• add prop for disabling default top inset application (#13114) (40b7e21) - by @​t0maboro

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

7.15.0 (2026-05-11)

Bug Fixes

• default multiselectable to undefined (cd466d4) - by @​satya164

Features

• update native tabs to use the new API in react-native-screens (a12db96) - by @​satya164

Changelog

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

7.16.0 (2026-05-25)

Features

• add prop for disabling default top inset application (#13114) (40b7e21) - by @​t0maboro

7.15.1 (2026-05-14)

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

7.15.0 (2026-05-11)

Bug Fixes

• default multiselectable to undefined (cd466d4) - by @​satya164

Features

• update native tabs to use the new API in react-native-screens (a12db96) - by @​satya164

7.14.14 (2026-05-08)

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

7.14.13 (2026-05-07)

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

Commits

• b89bba2 chore: publish
• 40b7e21 feat: add prop for disabling default top inset application (#13114)
• 8e0ce2b chore: publish
• b5b1f7c chore: publish
• cd466d4 fix: default multiselectable to undefined
• a12db96 feat: update native tabs to use the new API in react-native-screens
• 01ae31e chore: publish
• e8a05bb chore: publish
• See full diff in compare view

Updates @reduxjs/toolkit from 2.11.2 to 2.12.0

Release notes

Sourced from @​reduxjs/toolkit's releases.

v2.12.0

This feature release adds RTK usage skills files (via TanStack Intent) exports the RTK Query hook options types for reusability, fixes issues with infinite query status flags and batching handling, and makes some small TS improvements.

Changelog

Skills Files

We've generated agent skill files that are now included in the RTK package itself in a skills folder. They cover using and migrating to modern RTK, client and server state management, and handling side effects. You can point your agent at these skills yourself, or use TanStack Intent to pick them up.

TypeScript Improvements

The types for our RTK Query hook options are now exported, which lets you stop using Parameters to extract those types for use in your own code.

The types for listener middleware matchers were tweaked to allow interface-based type guards, not just type-based definitions.

The internal IgnorePaths type was renamed to IgnoredPaths for consistency.

We now use the built-in NoInfer util that comes with TS 5.4+.

Fixes

We fixed handling of the isSuccess status flag when switching infinite query cache entries. This should prevent accidental UI flashes that were occurring due to this flag accidentally flipping.

We've added a 100ms timeout fallback to the autoBatch enhancer's requestAnimationFrame timer. We had several reports that rAF didn't work correctly when used in background tabs / opened windows, and that RTK never updated the UI. This should ensure that the updates flush correctly.

What's Changed

• Export hook options types for RTK Query hooks by @​veeceey in reduxjs/redux-toolkit#5218
• Add TanStack Intent skills for Redux Toolkit by @​phryneas in reduxjs/redux-toolkit#5249
• Keep isSuccess: true when switching infinite query cache entries by @​riqts in reduxjs/redux-toolkit#5268
• fix: allow interface-based type guards as listener matcher by @​riqts in reduxjs/redux-toolkit#5269
• fix: add setTimeout fallback to raf autoBatch strategy for background tabs by @​riqts in reduxjs/redux-toolkit#5273
• chore(toolkit): rename IgnorePaths type to IgnoredPaths by @​Ri5ha6h in reduxjs/redux-toolkit#5284
• feat(toolkit)!: switch to native NoInfer utility type by @​aryaemami59 in reduxjs/redux-toolkit#5289

Full Changelog: reduxjs/redux-toolkit@v2.11.2...v2.12.0

Commits

• 576a02f Release 2.12.0
• de2d55e Merge pull request #5237 from aryaemami59/fix/codegen/generateEndpoints-retur...
• ac807c3 fix(codegen): narrow generateEndpoints return type
• 01ed3ba Merge pull request #5289 from aryaemami59/feat/toolkit/switch-to-native-NoInfer
• 1f16db1 Merge pull request #5290 from aryaemami59/build/toolkit/exclude-test-files-fr...
• 23783c1 build(toolkit): exclude test files from final bundle
• 91b8b0a feat(toolkit)!: switch to native NoInfer utility type
• 0b37f1a Merge pull request #5286 from aryaemami59/docs/toolkit/fix-typos
• 3cd62c8 fix unforwardedActions
• 64853cc chore: fix various typos
• Additional commits viewable in compare view

Updates fuse.js from 7.3.0 to 7.4.0

Release notes

Sourced from fuse.js's releases.

v7.4.0

First stable on the 7.4 line. Aggregates everything from the 7.4.0-beta.1 → 7.4.0-beta.8 cycle. See CHANGELOG.md for the per-beta breakdown.

Features

• FuseWorker — parallel search via Web Workers (9ba192c). New FuseWorker class shards the collection across workers, runs searches in parallel, and preserves the same result ordering as Fuse. See the Web Workers guide.
• token-search: tokenMatch: 'all' | 'any' option for AND/OR semantics (#827, 9f979d0). Default 'any' preserves existing behavior; 'all' requires every query word to match somewhere in a record (term-centric AND), useful for filter-style queries.
• token-search: customizable tokenizer with unicode-aware default (#821, 8e55cae). New tokenize?: RegExp | (text: string) => string[] option; the default regex now segments CJK, Cyrillic, Greek, Arabic, etc. out of the box.

Bug Fixes

• matches: report array-path keys as dotted strings (acd54e8). Previously match.key leaked a raw string[] for keys declared as path arrays (e.g. keys: [['author', 'firstName']]), contradicting the documented FuseResultMatch.key: string type. Now emits the canonical dotted string ('author.firstName'). Behavior change: consumers relying on the array shape need to update.
• bitap: restrict highlight indices to matched window (#792, 622f105). Closes #505, #611, #691, #793.
• index: correct doc-index alignment for Fuse<string> with blank docs (0b8e3ca).
• core: invalidate searcher cache on collection mutation (fcf4228).
• token-search: renumber inverted index after doc removal (ea9356d).
• workers: preserve global refIndex across shards (e4217f9), match Fuse ordering and reject non-cloneable options (d571390), reject useTokenSearch in FuseWorker (8c6183d).
• match: explicitly reject useTokenSearch in Fuse.match (3959d91).
• correct fieldCount accounting and add reverse lookup in inverted index (54e702c).
• guard against empty-string crash in fieldNorm (e550ab1); skip consecutive spaces in fieldNorm word counting (5929af6).
• types: resolve typecheck errors and align KeyStore types (dbc115d).
• docs: reflect data edits in playground demo (#825, 6eff909).

Performance

• reuse bit arrays in Bitap search instead of allocating per error level (ec9b446)
• replace forEach with for loops in search hot paths (1945f49)
• fast-path Math.pow when exponent is 1 in computeScore (c82de57)
• pre-allocate records array and use for loops in FuseIndex.create (5800036)
• replace regex with loop for word counting in fieldNorm (5517a9b)
• use filter instead of reverse-splice in removeAll / remove (c74823b, 8372b0a)
• token-search: drop unused postings from inverted index (5ea216f)

Internal

• refactor: replace extended-search matcher classes with plain functions (f8d61c9)
• bench: consolidate benchmark/ into bench/ and add npm scripts (3b3a4c6)
• ci: update Node matrix to 20, 22, 24 (b906906)
• chore(deps): pin secure versions via npm overrides (3a1b118)

Docs

• Migrated the site from VuePress to VitePress (663ee53)
• New articles: "Using Fuse.js with React" (512bc7d), "Fuse.js vs Semantic Search" (5f93b4d)
• New interactive demos in the fuzzy search article (edit distance, Bitap, threshold, search window)
• Web Workers documentation and demo
• Fuse Cloud landing page with waitlist

Behavior changes worth noting

... (truncated)

Changelog

Sourced from fuse.js's changelog.

7.4.0 (2026-05-30)

7.4.0-beta.8 (2026-05-25)

Bug Fixes

• matches: report array-path keys as dotted strings (acd54e8)

7.4.0-beta.7 (2026-05-22)

Features

• token-search: add tokenMatch 'all' | 'any' for AND/OR (#827) (9f979d0)

Bug Fixes

• docs: reflect data edits in playground demo (#825) (6eff909)

7.4.0-beta.6 (2026-05-14)

Bug Fixes

• bitap: restrict highlight indices to matched window (622f105), closes #792 #505 #611 #691 #793

7.4.0-beta.5 (2026-05-10)

Features

• token-search: add customizable tokenizer with unicode-aware default (8e55cae), closes #821

Bug Fixes

• index: correct doc-index alignment for Fuse with blank docs (0b8e3ca)

7.4.0-beta.4 (2026-04-28)

7.4.0-beta.3 (2026-04-26)

Bug Fixes

• match: explicitly reject useTokenSearch in Fuse.match (3959d91)
• workers: match Fuse ordering and reject non-cloneable options (d571390)
• workers: reject useTokenSearch in FuseWorker (8c6183d)

... (truncated)

Commits

• 77afcf3 chore(release): 7.4.0
• 3ef9328 chore(release): 7.4.0-beta.8
• acd54e8 fix(matches): report array-path keys as dotted strings
• 5985a7e style: reformat src and test with prettier 3
• 08bb3a7 chore: upgrade prettier to 3 and add format scripts
• 9417622 chore(release): 7.4.0-beta.7
• 9f979d0 feat(token-search): add tokenMatch 'all' | 'any' for AND/OR (#827)
• 6eff909 fix(docs): reflect data edits in playground demo (#825)
• a84f9cd docs: mention fuse-swift port and correct bundle sizes
• b08ad28 chore(release): 7.4.0-beta.6
• Additional commits viewable in compare view

Updates i18next from 26.0.8 to 26.3.0

Release notes

Sourced from i18next's releases.

v26.3.0

• feat(types): introduce ResourceNamespaceMap — a separate mergeable augmentation surface for namespace resource types, designed for monorepos where multiple packages each want to contribute their own namespaces. Previously, every package had to coordinate on a single CustomTypeOptions.resources declaration (or fall back to typing dependency namespaces as any) because resources is a single property of an interface and TypeScript reports TS2717 when two declarations of the same property disagree. The new interface merges naturally across declare module 'i18next' blocks, so each package can ship its own i18next.d.ts independently. Per-property merge handles same-namespace contributions from multiple packages, and same-key/different-literal conflicts are silently dropped to avoid poisoning t() overload resolution. Fully backwards-compatible — existing CustomTypeOptions.resources augmentations continue to work, and both surfaces can coexist. Scalar options (defaultNS, returnNull, enableSelector, etc.) still belong on CustomTypeOptions. Thanks @​sh3xu (#2434). Fixes #2409.

v26.2.0

• feat(types): new parseInterpolation TypeOption (default true). When set to false in CustomTypeOptions, the type-level extractor stops parsing translation strings for {{variable}} patterns. Required by i18next-icu users — the default extractor mistakes ICU MessageFormat nested-brace plurals like {count, plural, one {{count} row} other {{count} rows}} for an interpolation block and demands a phantom variable name. The flag is type-only; runtime interpolation is governed by InterpolationOptions and is unaffected. Fixes i18next-icu#85.
• fix(types): expose enableSelector on InitOptions so i18next.init({ enableSelector: 'strict' }) typechecks without a module augmentation. The runtime already reads opts?.enableSelector from init options; this lands the matching type declaration next to the other selector-resolution knobs. Accepts false | true | 'optimize' | 'strict'. Thanks @​Faithfinder (#2431)

v26.1.0

• feat: enableSelector: 'strict' (TypeOptions + runtime option). Opt-in mode that drops the flattened-primary form from NsResource at the type level — every namespace (primary included) is exposed only under its own key on $, uniformly across single- and multi-ns hooks. At runtime, a leading selector path segment matching the scope's namespace list is always rewritten as a namespace prefix, including the primary. Eliminates the silent-miss surface area where t($ => $.primary.foo) typechecks but doesn't resolve under the default mode (see #2429). Backward-compatible: default enableSelector: false | true | 'optimize' behavior is unchanged. Note: strict mode is incompatible with the #2405 pattern (keys whose names match sibling namespaces) — those users should stay on default mode.

v26.0.10

• feat: getFixedT accepts a fourth optional fixedOpts argument carrying scopeNs — the full namespace list the bound t was created for. The selector API uses scopeNs to detect when a path's first segment is a namespace prefix, without changing resolution scope. Resolution still uses the bound ns (a single primary string in the typical react-i18next setup), so plain t('key') lookups stay isolated to the primary namespace exactly as before — only t($ => $.secondaryNs.foo) selectors now route correctly under useTranslation([nsA, nsB]). Fixes the runtime side of #2429 for the react-i18next default-nsMode case. The 4th argument is opt-in: existing 3-arg getFixedT(lng, ns, keyPrefix) callers see no behavior change.

v26.0.9

• fix(types): unformatted interpolation values are now typed as string | number (was string). i18next stringifies values at runtime, so requiring callers to wrap numbers in String(...) for plain {{var}} placeholders was unnecessary friction — and could mask the real problem when a non-string value was passed alongside multiple interpolation slots (the t() overload resolution would fall through to the 3-arg form and report a confusing "not assignable to string" error against the options object). Typed format specifiers like {{x, number}}, {{x, currency}}, {{x, datetime}}, etc. keep their precise types; this only relaxes the no-format default. The count variable remains number-only

Changelog

Sourced from i18next's changelog.

26.3.0

• feat(types): introduce ResourceNamespaceMap — a separate mergeable augmentation surface for namespace resource types, designed for monorepos where multiple packages each want to contribute their own namespaces. Previously, every package had to coordinate on a single CustomTypeOptions.resources declaration (or fall back to typing dependency namespaces as any) because resources is a single property of an interface and TypeScript reports TS2717 when two declarations of the same property disagree. The new interface merges naturally across declare module 'i18next' blocks, so each package can ship its own i18next.d.ts independently. Per-property merge handles same-namespace contributions from multiple packages, and same-key/different-literal conflicts are silently dropped to avoid poisoning t() overload resolution. Fully backwards-compatible — existing CustomTypeOptions.resources augmentations continue to work, and both surfaces can coexist. Scalar options (defaultNS, returnNull, enableSelector, etc.) still belong on CustomTypeOptions. Thanks @​sh3xu (#2434). Fixes #2409.

26.2.0

• feat(types): new parseInterpolation TypeOption (default true). When set to false in CustomTypeOptions, the type-level extractor stops parsing translation strings for {{variable}} patterns. Required by i18next-icu users — the default extractor mistakes ICU MessageFormat nested-brace plurals like {count, plural, one {{count} row} other {{count} rows}} for an interpolation block and demands a phantom variable name. The flag is type-only; runtime interpolation is governed by InterpolationOptions and is unaffected. Fixes i18next-icu#85.
• fix(types): expose enableSelector on InitOptions so i18next.init({ enableSelector: 'strict' }) typechecks without a module augmentation. The runtime already reads opts?.enableSelector from init options; this lands the matching type declaration next to the other selector-resolution knobs. Accepts false | true | 'optimize' | 'strict'. Thanks @​Faithfinder (#2431)

26.1.0

• feat: enableSelector: 'strict' (TypeOptions + runtime option). Opt-in mode that drops the flattened-primary form from NsResource at the type level — every namespace (primary included) is exposed only under its own key on $, uniformly across single- and multi-ns hooks. At runtime, a leading selector path segment matching the scope's namespace list is always rewritten as a namespace prefix, including the primary. Eliminates the silent-miss surface area where t($ => $.primary.foo) typechecks but doesn't resolve under the default mode (see #2429). Backward-compatible: default enableSelector: false | true | 'optimize' behavior is unchanged. Note: strict mode is incompatible with the #2405 pattern (keys whose names match sibling namespaces) — those users should stay on default mode.

26.0.10

• feat: getFixedT accepts a fourth optional fixedOpts argument carrying scopeNs — the full namespace list the bound t was created for. The selector API uses scopeNs to detect when a path's first segment is a namespace prefix, without changing resolution scope. Resolution still uses the bound ns (a single primary string in the typical react-i18next setup), so plain t('key') lookups stay isolated to the primary namespace exactly as before — only t($ => $.secondaryNs.foo) selectors now route correctly under useTranslation([nsA, nsB]). Fixes the runtime side of #2429 for the react-i18next default-nsMode case. The 4th argument is opt-in: existing 3-arg getFixedT(lng, ns, keyPrefix) callers see no behavior change.

26.0.9

• fix(types): unformatted interpolation values are now typed as string | number (was string). i18next stringifies values at runtime, so requiring callers to wrap numbers in String(...) for plain {{var}} placeholders was unnecessary friction — and could mask the real problem when a non-string value was passed alongside multiple interpolation slots (the t() overload resolution would fall through to the 3-arg form and report a confusing "not assignable to string" error against the options object). Typed format specifiers like {{x, number}}, {{x, currency}}, {{x, datetime}}, etc. keep their precise types; this only relaxes the no-format default. The count variable remains number-only

Commits

• bdf651c 26.3.0
• 988a362 changelog: 26.3.0 entry for #2434
• 159506c feat(types): introduce ResourceNamespaceMap for monorepo namespace augmentati...
• df68b1f ci: restore JSR publishing via GitHub Actions OIDC
• 22fb6ad 26.2.0
• b640ac4 feat(types): parseInterpolation flag for ICU-friendly t() typing (i18next-icu...
• 0b9debd changelog: 26.1.1 entry for #2431
• 50509e4 fix(types): expose enableSelector on InitOptions (#2431)
• 80b5402 Enhance Pro Tip in README with i18next-locize-backend plugin link
• 5af0475 26.1.0
• Additional commits viewable in compare view

Updates react-i18next from 17.0.6 to 17.0.8

Changelog

Sourced from react-i18next's changelog.

17.0.8

• fix(types): <Trans i18nKey={$ => ...}> now typechecks under enableSelector: 'strict'. The Trans component's conditional type was gated on _EnableSelector extends true | 'optimize', excluding 'strict' and falling back to the legacy string-key signature. Runtime was already correct (it calls keyFromSelector(i18nKey) whenever typeof i18nKey === 'function'); this is a type-only fix that widens the conditional to include 'strict'. Thanks @​Faithfinder (#1921)

17.0.7

• feat: useTranslation([nsA, nsB, ...]) now passes its full namespace list to getFixedT via the new scopeNs opt (requires i18next ≥ v26.0.10). This makes selector calls with a secondary-namespace prefix resolve correctly under default nsMode: t($ => $.nsB.foo) previously missed silently because the bound ns was the primary string only and i18next's selector rewrite needed an array. Resolution semantics are unchanged — plain t('key') lookups still stay isolated to the primary namespace by default; use nsMode: 'fallback' to opt into multi-ns fallback resolution as before. Fixes i18next#2429 for useTranslation-based callers.

Commits

• a46ad23 17.0.8
• f715031 update i18next dep
• a515d5b changelog: 17.0.8 entry for #1921
• d5ab7c8 fix(types): accept selector i18nKey on <Trans> under enableSelector: 'strict'...
• b91ba36 Add Locize advice section near the top of README
• 5e892a2 17.0.7
• c8f4c6b feat: useTranslation([nsA,nsB]) routes selector secondary-ns prefix via getFi...
• 084f9a6 Modernize locize.com URLs and refresh UTM tags
• See full diff in compare view

Updates react-native-charts-wrapper from 0.6.0 to 0.7.0

Release notes

Sourced from react-native-charts-wrapper's releases.

Upgrade to support React Native 0.81+ and Fabric architecture

Commits

• f99037f Feature/new architecture support (#1018)
• bde0a10 Update package.json (#984)
• a21e3db Update CandleDataExtract.swift (#985)
• See full diff in compare view

Updates react-native-paper from 5.15.1 to 5.15.3

Release notes

Sourced from react-native-paper's releases.

Release 5.15.3

5.15.3 (2026-05-26)

Bug Fixes

• animated-fab: correct Android shadow/content stacking (#4903) (bf20edb)
• progress-bar: preserve fill border radius while animating progress (#4950) (bf880da)

Release 5.15.2

5.15.2 (2026-05-08)

Bug Fixes

• fix portals, dialogs & modals not correctly positioned on react native 0.85 (#4906) (2fea2cd)

Commits

• 7f3803c chore: release 5.15.3
• 2a5715a ci: convert CircleCi to Github workflows (#4884)
• bf880da fix(progress-bar): preserve fill border radius while animating progress (#4950)
• bf20edb fix(animated-fab): correct Android shadow/content stacking (#4903)
• 16a69a7 chore: release 5.15.2
• 2fea2cd fix: fix portals, dialogs & modals not correctly positioned on react native 0...
• See full diff in compare view

Updates react-native-paper-dates from 0.23.6 to 0.23.9

Release notes

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

Release 0.23.9

What's Changed

• Add unique testIDs to DatePickerModal IconButtons by @​Copilot in web-ridge/react-native-paper-dates#529

Full Changelog: web-ridge/react-native-paper-dates@v0.23.8...v0.23.9

Release 0.23.8

What's Changed

• fix: use dark scrollbar in dark mode on web by @​iM-GeeKy in web-ridge/react-native-paper-dates#527

Full Changelog: web-ridge/react-native-paper-dates@v0.23.6...v0.23.8

Commits

• bb3dec1 chore: release 0.23.9
• 32d2dc5 Merge pull request #529 from web-ridge/copilot/fix-date-picker-modal-icons
• 214fe1a chore: remove accidentally added package-lock.json
• c21c31a fix: add unique testIDs to DatePickerModal IconButtons
• 0f1f64b Initial plan
• 5950629 chore: release 0.23.8
• c2ed57f fix: use dark scrollbar in dark mode on web (#527)
• See full diff in compare view

Updates react-native-reanimated from 4.3.0 to 4.4.0

Release notes

Sourced from react-native-reanimated's releases.

Reanimated - 4.4.0

Key changes

iOS CSS Core Animation

Reanimated 4.4.0 introduces a new platform-backed CSS animation engine on iOS that runs animations directly on Core Animation layers instead of going through the JS-driven update loop. It is hidden behind the IOS_CSS_CORE_ANIMATION static feature flag.

• feat: Wire CSSPlatformTransition with iOS platform implementation by @​MatiPl01 in software-mansion/react-native-reanimated#9325
• chore: Hide platform animations behind a feature flag by @​MatiPl01 in software-mansion/react-native-reanimated#9493

Animation Backend

A new Animation Backend has been integrated behind a feature flag, which will help greatly with the flow of updating the Shadow Tree in animations.

• Integrate Animation Backend behind a flag by @​bartlomiejbloniarz in software-mansion/react-native-reanimated#9279

New useTimestamp hook

A new useTimestamp hook exposes the current frame timestamp as a Shared Value that updates every frame with the time elapsed since the first frame, with...

Description has been truncated