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

[dependabot]

Bumps the production-dependencies group with 15 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
i18next	26.0.8	26.2.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.2
react-native-paper-dates	0.23.6	0.23.9
react-native-reanimated	4.3.0	4.3.1
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-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 i18next from 26.0.8 to 26.2.0

Release notes

Sourced from i18next's releases.

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.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

• 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
• 85c0951 feat: enableSelector: 'strict' — explicit-ns selector mode, no flattened prim...
• 8fec684 docs(types): clarify ExistsFunction note re: narrowing through wrappers
• 61eaf5b 26.0.10
• 47fd92f feat: getFixedT 4th-arg scopeNs decouples selector ns-detection from resoluti...
• 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

Commits

• See full diff in compare view

Updates react-native-paper from 5.15.1 to 5.15.2

Release notes

Sourced from react-native-paper's releases.

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

• 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.3.1

Release notes

Sourced from react-native-reanimated's releases.

Reanimated - 4.3.1

What's Changed

• cherry-pick(Reanimated): Incorrect CSS props reverting on CSS transition detach (#9220) by @​MatiPl01 in software-mansion/react-native-reanimated#9288
• cherry-pick(Reanimated): Fix animation cancellation race condition missing code (#9242) by @​MatiPl01 in software-mansion/react-native-reanimated#9289
• cherry-pick(4.3-stable): workflow for OIDC publishing (#9095) by @​tjzel in software-mansion/react-native-reanimated#9298
• cherry-pick(4.3-stable): useScrollOffset on renderScrollComponent (#9286) by @​tjzel in software-mansion/react-native-reanimated#9299
• cherry-pick(Reanimated): Fix Unistyles flattening regression in 4.3.0 (#9284) by @​MatiPl01 in software-mansion/react-native-reanimated#9301
• cherry-pick(4.3-stable): fix registries race conditions (#9323) by @​tjzel in software-mansion/react-native-reanimated#9349
• release(Reanimated): 4.3.1 by @​tjzel in software-mansion/react-native-reanimated#9353

Full Changelog: software-mansion/react-native-reanimated@4.3.0...4.3.1

Commits

• b349631 release(Reanimated): 4.3.1
• 177650b fix: OIDC releases not including type declarations (#9348)
• 6dd6729 fix(Reanimated): registries race conditions (#9323)
• d889209 cherry-pick(Reanimated): Fix Unistyles flattening regression in 4.3.0 (#928...
• ce0460b cherry-pick(4.3-stable): useScrollOffset on renderScrollComponent (#9286) (#9...
• f8a5240 feat: workflow for OIDC publishing (#9095)
• 9cad57e cherry-pick(Reanimated): Fix animation cancellation race condition missing co...
• a12d1ef cherry-pick(Reanimated): Incorrect CSS props reverting on CSS transition deta...
• See full diff in compare view

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

Release notes

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

Release 5.8.0

5.8.0 (2026-05-18)

Changes

• remove UIImplementation usage from SafeAreaView (#730) (ef89f4d)

Commits

• 5a9ad5e chore: release 5.8.0
• ef89f4d fix: remove UIImplementation usage from SafeAreaView (#730)
• 93b7a32 ci: add Windows matrix to Android build (#726)
• 3ec2ff3 chore(docs): fix typo in SafeAreaView api reference (#718)
• 843e5b9 Added gemfile and updated podfile.lock (#696)
• See full diff in compare view

Updates react-native-screens from 4.24.0 to 4.25.2

Release notes

Sourced from react-native-screens's releases.

4.25.2

What's changed

Patch release bringing two important fixes.

Bug fixes 🐞

• fix(Android, Tabs): trigger appearance update on user tab selection (#4075)
• fix(Android, FormSheet): include keyboard translationY in shadow update (#4065)

Full Changelog: software-mansion/react-native-screens@4.25.1...4.25.2

4.25.1

What's Changed

Patch version with some crucial fixes.

Bug fixes 🐞

• fix(Android, Tabs): handle Tabs reattachment to window (#4035)
• fix(Android, FormSheet): Prioritize keyboard animation over content resize animation (#3924)
• refactor(Android, FormSheet): Align animators implementation to use ValueAnimator (#3922)
• refactor(Android, FormSheet): Minor cleanups in SheetAnimationCoordinator (#3921)
• fix(Android, FormSheet): Create SheetAnimationCoordinator to synchronize animations coming from different sources (#3914)

Full Changelog: software-mansion/react-native-screens@4.25.0...4.25.1

4.25.0

What's Changed

Minor release, bringing golden version of Tabs API. Unless we get your negative feedback, we plan to stabilise Tabs API in next minor.

[!important] 4.25.0 no longer supports the legacy architecture. Most likely, the library will simply fail to build.

This release brings important Tabs API changes in JS and native layer, required for stabilisation of the API. Downstream libraries are already in advanced stage of adaptation to these changes. Please track the releases of your navigation solution for compatibility remarks.

Improvements

• feat(Tabs): remove freezeContents & placeholder props by @​kkafar in software-mansion/react-native-screens#3673
• feat(Android, Tabs): Add support for selectedIcon on Android by @​t0maboro in software-mansion/react-native-screens#3633
• chore: define min. required react-native version in peerDependencies by @​kkafar in software-mansion/react-native-screens#3691
• chore(readme): update supported RN versions in readme (drop legacy arch) by @​kkafar in software-mansion/react-native-screens#3692
• feat: add ScrollViewMarker experimental component by @​kkafar in software-mansion/react-native-screens#3674
• chore: rename TabsAccessory to TabsBottomAccessory by @​kligarski in software-mansion/react-native-screens#3712
• chore(iOS, Split): align naming for native components by @​sgaczol in software-mansion/react-native-screens#3695
• feat(Android, Tabs): State-driven appearance on Android by @​t0maboro in software-mansion/react-native-screens#3714

... (truncated)

Commits

• a9d5735 fix(Android, Tabs): trigger appearance update on user tab selection (#4075)
• c58b6d4 fix(Android, FormSheet): include keyboard translationY in shadow update (#4065)
• a00b359 Remove import of test 3910
• 8722518 fix(Android, Tabs): handle Tabs reattachment to window (#4035)
• c2172be fix(Android, FormSheet): Prioritize keyboard animation over content resize an...
• fa54825 refactor(Android, FormSheet): Align animators implementation to use ValueAnim...
• 1258d2b refactor(Android, FormSheet): Minor cleanups in SheetAnimationCoordinator (#3...
• 2565173 fix(Android, FormSheet): Create SheetAnimationCoordinator to synchronize anim...
• dfd36e1 chore: revert "chore: cherry-pick changes to 4.25.1 stable" (#4055)
• 0b200fd chore: cherry-pick changes to 4.25.1 stable (#4054)
• Additional commits viewable in compare view

Updates react-native-svg from 15.15.4 to 15.15.5

Release notes

Sourced from react-native-svg's releases.

v15.15.5

This release includes minor fixes and improvements across all platforms, along with the OIDC setup.

What's Changed

• fix: clang-diagnostic-inconsistent-missing-override error in Imageview… by @​acoates-ms in software-mansion/react-native-svg#2939
• fix: render SVG on macOS Fabric by opting out of updateLayer by @​gabrieldonadel in software-mansion/react-native-svg#2941
• refactor: drop warn-once dependency by @​jakex7 in software-mansion/react-native-svg#2946
• chore: bump tests-example to react-native@0.85.3 by @​jakex7 in software-mansion/react-native-svg#2945
• ci: Setup publishing workflow by @​jakex7 in software-mansion/react-native-svg#2947
• chore: remove release-it package by @​jakex7 in software-mansion/react-native-svg#2950
• fix(android): fix MaskView broken when enabling RN props 2.0 by @​hannojg in software-mansion/react-native-svg#2948
• fix(android): fix LinearGradient when enabling RN props 2.0 by @​hannojg in software-mansion/react-native-svg#2949
• ci: add RNRepo to ci builds by @​radoslawrolka in software-mansion/react-native-svg#2944
• fix: apply opacity to currentColor for fill and stroke on Apple platforms by @​davor-bauk-sh in software-mansion/react-native-svg#2923
• fix: update repository URL by @​jakex7 in software-mansion/react-native-svg#2957
• Release 15.15.5 by @​jakex7 in software-mansion/react-native-svg#2956

New Contributors

• @​hannojg made their first contribution in software-mansion/react-native-svg#2948
• @​radoslawrolka made their first contribution in software-mansion/react-native-svg#2...

  Description has been truncated

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.