Skip to content

chore: bump the dependencies group with 15 updates#8

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/dependencies-b64cd8e452
Open

chore: bump the dependencies group with 15 updates#8
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/dependencies-b64cd8e452

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot bot commented on behalf of github Apr 1, 2026

Bumps the dependencies group with 15 updates:

Package From To
@react-native-async-storage/async-storage 2.2.0 3.0.2
@rn-primitives/portal 1.3.0 1.4.0
i18next 25.10.10 26.0.3
lucide-react-native 0.575.0 1.7.0
react 19.2.0 19.2.4
react-dom 19.2.0 19.2.4
react-i18next 16.6.6 17.0.2
react-native 0.83.2 0.84.1
react-native-reanimated 4.2.1 4.3.0
react-native-safe-area-context 5.6.2 5.7.0
react-native-screens 4.23.0 4.24.0
react-native-svg 15.15.3 15.15.4
react-native-worklets 0.7.2 0.8.1
tailwindcss 3.4.19 4.2.2
typescript 5.9.3 6.0.2

Updates @react-native-async-storage/async-storage from 2.2.0 to 3.0.2

Release notes

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

Async Storage v3.0.2

Patch Changes

  • 1d1867f: include jest mock

Async Storage v3.0.1

Patch Changes

  • 7b64ea4: missing build step from CI added

Async Storage v3.0.0

‼️ Due to missing native artifacts, please do not use this version - 3.0.1 contains a fix!

Major Changes

  • Release of version v3. Please visit Async Storage docs to learn more

    Breaking changes:

    • Async Storage uses "scoped storages", where you need to create a storage instance before using it
    • Default export is a singleton storage that uses v2/v1 storage, for easier transition
    • An extra installation step is required for android
    • callback based API is dropped
    • Methods for batch operations (formerly multi* methods) have been renamed and their API updated
    • useAsyncStorage hook has been removed (will be introduced later)
    • Updated Native side (Brownfield) access to storage - dropped apple's delegate
    • Dropped a flag to opt out from iCloud backup - disabled by default now

3.0.0-next.0

Initial release of upcoming version v3. Please visit Async Storage docs to learn more

Breaking changes:

  • Async Storage uses "scoped storages", where you need to create a storage instance before using it
  • Default export is a singleton storage that uses v2/v1 storage, for easier transition
  • An extra installation step is required for android
  • callback based API is dropped
  • Methods for batch operations (formerly multi* methods) have been renamed and their API updated
  • useAsyncStorage hook has been removed (will be introduced later)
  • Updated Native side (Brownfield) access to storage - dropped apple's delegate
  • Dropped a flag to opt out from iCloud backup - disabled by default now
Changelog

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

3.0.2

Patch Changes

  • 1d1867f: include jest mock

3.0.1

Patch Changes

  • 7b64ea4: missing build step from CI added

3.0.0

Major Changes

  • f100276: Initial release of upcoming version v3. Please visit Async Storage docs to learn more

    Breaking changes:

    • Async Storage uses "scoped storages", where you need to create a storage instance before using it
    • Default export is a singleton storage that uses v2/v1 storage, for easier transition
    • An extra installation step is required for android
    • callback based API is dropped
    • Methods for batch operations (formerly multi* methods) have been renamed and their API updated
    • useAsyncStorage hook has been removed (will be introduced later)
    • Updated Native side (Brownfield) access to storage - dropped apple's delegate
    • Dropped a flag to opt out from iCloud backup - disabled by default now

Patch Changes

  • e9061f9: fix: re-deploy android
  • 6ffa4d9: Fixes crashes on ios 16 and below due to unescaped urls
  • 300cba3: update ios setup for cocoapods

3.0.0-next.3

Patch Changes

  • 6ffa4d9: Fixes crashes on ios 16 and below due to unescaped urls

3.0.0-next.2

Patch Changes

  • e9061f9: fix: re-deploy android

3.0.0-next.1

Patch Changes

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for @​react-native-async-storage/async-storage since your current version.

Install script changes

This version adds prepare script that runs during installation. Review the package contents before updating.


Updates @rn-primitives/portal from 1.3.0 to 1.4.0

Updates i18next from 25.10.10 to 26.0.3

Release notes

Sourced from i18next's releases.

v26.0.3

  • fix(types): addResourceBundle now accepts an optional 6th options parameter ({ silent?: boolean; skipCopy?: boolean }) matching the runtime API 2419

v26.0.2

  • fix(types): t("key", {} as TOptions) no longer produces a type error — the context constraint now bypasses strict checking when context is unknown (e.g. from TOptions) 2418

v26.0.1

  • fix: Formatter no longer crashes when alwaysFormat is true and no format specifier is present (format is undefined)
  • fix: Formatter now returns undefined/null values as-is instead of producing NaN when the value is missing

v26.0.0

This is a major breaking release:

Breaking Changes

  • Remove deprecated initImmediate option — the backward-compatibility mapping from initImmediate to initAsync (introduced in v24) has been removed. Use initAsync instead.
  • Remove legacy interpolation.format function — the old monolithic format function (interpolation: { format: (value, format, lng) => ... }) is no longer supported. The built-in Formatter (or a custom Formatter module via .use()) is now always used. Migrate to the new formatting approach using i18next.services.formatter.add() or .addCached() for custom formatters.
  • Remove console support notice — the console support notice introduced in v25.8.0 has been removed, along with the showSupportNotice option and all related internal suppression logic (globalThis.__i18next_supportNoticeShown, I18NEXT_NO_SUPPORT_NOTICE env var). See our blog post for the full story.
  • Remove simplifyPluralSuffix option — this option was unused by the core PluralResolver (which relies entirely on Intl.PluralRules). It only had an effect in the old v1/v2/v3 compatibility layer. The v4 test compatibility layer now defaults to true internally.
  • Remove deprecated @babel/polyfill from devDependencies.

Improvements

  • Code modernization across all source files:
    • Replace indexOf() > -1 / indexOf() < 0 with .includes() (~40+ occurrences)
    • Replace indexOf() === 0 with .startsWith() where appropriate
    • Replace var with const, '' + object with String(object), .substring() with .slice()
    • Replace .apply(observer, [event, ...args]) with direct call observer(event, ...args)
    • Remove unnecessary .call(this, ...) in BackendConnector retry logic
    • Fix array-callback-return in LanguageUtils getBestMatchFromCodes
    • Clean up all stale eslint-disable comments from source files
  • EventEmitter: add once() method for one-time event subscriptions
  • Memory leak fix: move module-level checkedLoadedFor cache to Translator instance, preventing cross-instance state leakage
  • TypeScript: fix BackendModule generic parameter naming inconsistency between CJS and ESM type definitions
  • TypeScript: add once() method to i18n and ResourceStore type interfaces
  • ESLint 9: migrate from ESLint 8 (airbnb-base) to ESLint 9 flat config with neostandard
  • Vitest 4: upgrade from vitest 3 to vitest 4, migrate workspace files to test.projects config
Changelog

Sourced from i18next's changelog.

26.0.3

  • fix(types): addResourceBundle now accepts an optional 6th options parameter ({ silent?: boolean; skipCopy?: boolean }) matching the runtime API 2419

26.0.2

  • fix(types): t("key", {} as TOptions) no longer produces a type error — the context constraint now bypasses strict checking when context is unknown (e.g. from TOptions) 2418

26.0.1

  • fix: Formatter no longer crashes when alwaysFormat is true and no format specifier is present (format is undefined)
  • fix: Formatter now returns undefined/null values as-is instead of producing NaN when the value is missing

26.0.0

This is a major breaking release:

Breaking Changes

  • Remove deprecated initImmediate option — the backward-compatibility mapping from initImmediate to initAsync (introduced in v24) has been removed. Use initAsync instead.
  • Remove legacy interpolation.format function — the old monolithic format function (interpolation: { format: (value, format, lng) => ... }) is no longer supported. The built-in Formatter (or a custom Formatter module via .use()) is now always used. Migrate to the new formatting approach using i18next.services.formatter.add() or .addCached() for custom formatters.
  • Remove console support notice — the console support notice introduced in v25.8.0 has been removed, along with the showSupportNotice option and all related internal suppression logic (globalThis.__i18next_supportNoticeShown, I18NEXT_NO_SUPPORT_NOTICE env var). See our blog post for the full story.
  • Remove simplifyPluralSuffix option — this option was unused by the core PluralResolver (which relies entirely on Intl.PluralRules). It only had an effect in the old v1/v2/v3 compatibility layer. The v4 test compatibility layer now defaults to true internally.
  • Remove deprecated @babel/polyfill from devDependencies.

Improvements

  • Code modernization across all source files:
    • Replace indexOf() > -1 / indexOf() < 0 with .includes() (~40+ occurrences)
    • Replace indexOf() === 0 with .startsWith() where appropriate
    • Replace var with const, '' + object with String(object), .substring() with .slice()
    • Replace .apply(observer, [event, ...args]) with direct call observer(event, ...args)
    • Remove unnecessary .call(this, ...) in BackendConnector retry logic
    • Fix array-callback-return in LanguageUtils getBestMatchFromCodes
    • Clean up all stale eslint-disable comments from source files
  • EventEmitter: add once() method for one-time event subscriptions
  • Memory leak fix: move module-level checkedLoadedFor cache to Translator instance, preventing cross-instance state leakage
  • TypeScript: fix BackendModule generic parameter naming inconsistency between CJS and ESM type definitions
  • TypeScript: add once() method to i18n and ResourceStore type interfaces
  • ESLint 9: migrate from ESLint 8 (airbnb-base) to ESLint 9 flat config with neostandard
  • Vitest 4: upgrade from vitest 3 to vitest 4, migrate workspace files to test.projects config
Commits
  • ea8391c 26.0.3
  • 5da85e0 fix(types): addResourceBundle now accepts an optional 6th options paramet...
  • 3db098f 26.0.2
  • 6ece798 fix(types): t("key", {} as TOptions) no longer produces a type error — the ...
  • 18b3dbb 26.0.1
  • c829f91 fix: Formater crashes etc.
  • 1593d11 remove node v18 from github actions
  • d85c23d 26.0.0
  • fad19d5 feat!: v26.0.0 — major version with breaking changes
  • 780aa91 jsr update
  • See full diff in compare view

Updates lucide-react-native from 0.575.0 to 1.7.0

Release notes

Sourced from lucide-react-native's releases.

Version 1.7.0

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@1.6.0...1.7.0

Version 1.6.0

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@1.5.0...1.6.0

Version 1.5.0

What's Changed

Full Changelog: lucide-icons/lucide@1.4.0...1.5.0

Version 1.4.0

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@1.3.0...1.4.0

Version 1.3.0

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@1.2.0...1.3.0

Version 1.2.0

What's Changed

New Contributors

... (truncated)

Commits

Updates react from 19.2.0 to 19.2.4

Release notes

Sourced from react's releases.

19.2.4 (January 26th, 2026)

React Server Components

19.2.3 (December 11th, 2025)

React Server Components

19.2.2 (December 11th, 2025)

React Server Components

19.2.1 (December 3rd, 2025)

React Server Components

Changelog

Sourced from react's changelog.

19.2.1 (Dec 3, 2025)

React Server Components

Commits

Updates react-dom from 19.2.0 to 19.2.4

Release notes

Sourced from react-dom's releases.

19.2.4 (January 26th, 2026)

React Server Components

19.2.3 (December 11th, 2025)

React Server Components

19.2.2 (December 11th, 2025)

React Server Components

19.2.1 (December 3rd, 2025)

React Server Components

Changelog

Sourced from react-dom's changelog.

19.2.1 (Dec 3, 2025)

React Server Components

Commits

Updates react-i18next from 16.6.6 to 17.0.2

Changelog

Sourced from react-i18next's changelog.

17.0.2

  • fix(types): values prop on <Trans /> now only requires interpolation variables for the specific i18nKey, not all variables in the namespace 1913

17.0.1

  • chore: bump minimum i18next peer dependency to >= 26.0.1 (forgot to do it in last version)
  • fix: migrate test setup from removed legacy interpolation.format to i18n.services.formatter.add() (i18next v26)

17.0.0

Potentially breaking changes

  • fix: transKeepBasicHtmlNodesFor now correctly preserves HTML tag names when children contain interpolations or mixed content 230
    • Previously, <strong>{{name}}</strong> was incorrectly serialized as <1>{{name}}</1> — the tag name was only preserved for plain string children
    • This bug existed since the feature was introduced and affects auto-generated keys (when no explicit i18nKey is provided)
    • If you rely on auto-generated Trans keys containing indexed tags for kept HTML elements with interpolation children, you will need to update your translation files

Other changes

  • updated dev dependencies (vitest, rollup plugins, happy-dom, typescript, etc.)
Commits
  • 4d62f86 17.0.2
  • 61fe80c fix(types): values prop on \<Trans /> now only requires interpolation vari...
  • b58d5a5 l10n: add Swedish language support to examples (#1912)
  • 2321496 17.0.1
  • 7e656b5 chore: bump minimum i18next peer dependency
  • dfc350b upate github actions
  • 7fe2620 17.0.0
  • f4ada4c fix: transKeepBasicHtmlNodesFor now correctly preserves HTML tag names when...
  • See full diff in compare view

Updates react-native from 0.83.2 to 0.84.1

Release notes

Sourced from react-native's releases.

0.84.1

Fixed

Android specific

  • Fix included-build gradle.properties resolution for monorepos by reading from parent Gradle start parameters (projectDir/currentDir) before falling back to ../../android/gradle.properties, so hermesV1Enabled can be inherited correctly. (c5ae0c820a by @​Titozzz)
  • Provide symbol fallbacks for inspector-modern/chrome/Registration.h when HermesV1 is disabled. (5ee695ad8f by @​tjzel)
  • ReactPlugin.kt always setting hermesV1Enabled to true (45896674d1 by @​tjzel)

Hermes dSYMS:

Hermes V1 dSYMS:

ReactNativeDependencies dSYMs:

ReactNative Core dSYMs:

You can file issues or pick requests against this release here.

To help you upgrade to this version, you can use the Upgrade Helper ⚛️.

View the whole changelog in the CHANGELOG.md file.

0.84.0

Hermes dSYMS:

Hermes V1 dSYMS:

... (truncated)

Changelog

Sourced from react-native's changelog.

Changelog

v0.85.0-rc.7

Fixed

iOS specific

  • Hermes: Fix Hermes crash when async void TurboModule method throws NSException by re-throwing instead of converting to JSError on wrong thread (4083a6ff92 by @​fabriziocucci)

v0.85.0-rc.6

Changed

iOS specific

Fixed

iOS specific

v0.85.0-rc.5

Fixed

iOS specific

v0.85.0-rc.1

Breaking

Added

v0.85.0-rc.0

Breaking

... (truncated)

Commits
  • 6064933 Release 0.84.1
  • 2c65dd7 Fix flaky Modal-itest by adding proper root cleanup (#55712)
  • 938a338 Attempt to reduce flakyness on Modal-itest "MessageQueue is not empty" failur...
  • 3483f16 [LOCAL] Bump hermes v1 version
  • d965609 fix(react-native): resolve included-build gradle.properties from parent build...
  • 3c503a8 fix: missing symbols on prebuilt Android with hermesV1 disabled (#55400)
  • 9b79d39 [LOCAL] Fix misaligned Hermes version
  • 5693f60 Release 0.84.0
  • 5c69e21 Release 0.84.0-rc.5
  • 3552d65 [LOCAL] Bump Hermes version
  • Additional commits viewable in compare view

Updates react-native-reanimated from 4.2.1 to 4.3.0

Release notes

Sourced from react-native-reanimated's releases.

Reanimated - 4.3.0

Key changes

CSS SVG Animations

CSS animations now support animating SVG components and their properties, including Path, Image, LinearGradient, RadialGradient, Pattern and Text. This includes support for animating the d property of Path components with a special handling for path morphing.

Shared Value re-implementation

Shared Value internal implementation changed - now it uses Shareable type from react-native-worklets as its internal value container. That means you can finally use Shared Values from other Worklet Runtimes than just the UI Runtime. Also USE_SYNCHRONIZABLE_IN_MUTABLE optimization feature flag is now enabled by default.

Animated Styles type changes

TypeScript type of Animated Styles now makes it impossible to accidentally pass them to non-animated components. This replaces previous runtime-check for this kind of mistake, which proved to be prone to false positives.

Fixes

... (truncated)

Commits
  • 63fa5df release(Reanimated): 4.3.0
  • 98c5ef4 fix(Reanimated): RCTModernEventEmmitter for older RN (#9181)
  • 0db42e4 Merge branch 'main' into @​tjzel/4.3-stable/merge-main
  • 5f9b4d0 chore: pre-release example cleanup and fixes (#9178)
  • a215ea7 Remove dead code in build.gradle (#9177)
  • dc18bf0 chore: Remove unused hasProp function, improve transformOrigin processor ...
  • a25481f chore: Use 'worklet' directive directly in processor functions (#9154)
  • 681a4fa chore: useHandler reimplementation (#9090)
  • 96222de fix - passing negative values to filter crashes on iOS (#9155)
  • a05745f chore(Rea): migrate to RCTModernEventEmitter (#9033)
  • Additional commits viewable in compare view

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

Release notes

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

Release 5.7.0

5.7.0 (2026-02-24)

Bug Fixes

  • make SafeAreaView respect edges param on web (#685) (db1bdcb)

Features

Commits
Maintainer changes

This version was pushed to npm by melvalesca, a new releaser for react-native-safe-area-context since your current version.


Updates react-native-screens from 4.23.0 to 4.24.0

Release notes

Sourced from react-native-screens's releases.

4.24.0

What's Changed

Minor release bringing further development to 5.0 stack implementation, nice improvements to Split API and other various improvements & fixes.

[!caution] Most importantly this is the last release we've tested with legacy architecture.

From 4.25.0 on, we no longer plan to support RN versions below 0.82, which naturally comes with drop of support for legacy arch. We plan to gradually remove the legacy architecture related code.

I want to also announce our plans regarding approach to 5.0 transition. At the moment we plan to keep releasing v4 line till we're "close to ready" with all APIs we've planed for 5.0 major. We plan to stabilise Tabs API on v4 line. When we're "close to ready" we'll release a series (rather not many) of 5.0-alpha/beta versions & after 5.0 stable release v4 branch will stay for some, not long, time in maintenance mode. The downstream library implementers are already adopting new 5.0 APIs, they should be available for testing in the navigation library of your choice shortly.

✅ Improvements

🐞 Bug fixes

@dependabot
chore: bump the dependencies group with 15 updates
3d5805f 
Bumps the dependencies group with 15 updates:

| Package | From | To |
| --- | --- | --- |
| [@react-native-async-storage/async-storage](https://github.com/react-native-async-storage/async-storage/tree/HEAD/packages/async-storage) | `2.2.0` | `3.0.2` |
| @rn-primitives/portal | `1.3.0` | `1.4.0` |
| [i18next](https://github.com/i18next/i18next) | `25.10.10` | `26.0.3` |
| [lucide-react-native](https://github.com/lucide-icons/lucide/tree/HEAD/packages/lucide-react-native) | `0.575.0` | `1.7.0` |
| [react](https://github.com/facebook/react/tree/HEAD/packages/react) | `19.2.0` | `19.2.4` |
| [react-dom](https://github.com/facebook/react/tree/HEAD/packages/react-dom) | `19.2.0` | `19.2.4` |
| [react-i18next](https://github.com/i18next/react-i18next) | `16.6.6` | `17.0.2` |
| [react-native](https://github.com/facebook/react-native/tree/HEAD/packages/react-native) | `0.83.2` | `0.84.1` |
| [react-native-reanimated](https://github.com/software-mansion/react-native-reanimated/tree/HEAD/packages/react-native-reanimated) | `4.2.1` | `4.3.0` |
| [react-native-safe-area-context](https://github.com/AppAndFlow/react-native-safe-area-context) | `5.6.2` | `5.7.0` |
| [react-native-screens](https://github.com/software-mansion/react-native-screens) | `4.23.0` | `4.24.0` |
| [react-native-svg](https://github.com/react-native-community/react-native-svg) | `15.15.3` | `15.15.4` |
| [react-native-worklets](https://github.com/software-mansion/react-native-reanimated/tree/HEAD/packages/react-native-worklets) | `0.7.2` | `0.8.1` |
| [tailwindcss](https://github.com/tailwindlabs/tailwindcss/tree/HEAD/packages/tailwindcss) | `3.4.19` | `4.2.2` |
| [typescript](https://github.com/microsoft/TypeScript) | `5.9.3` | `6.0.2` |


Updates `@react-native-async-storage/async-storage` from 2.2.0 to 3.0.2
- [Release notes](https://github.com/react-native-async-storage/async-storage/releases)
- [Changelog](https://github.com/react-native-async-storage/async-storage/blob/main/packages/async-storage/CHANGELOG.md)
- [Commits](https://github.com/react-native-async-storage/async-storage/commits/@react-native-async-storage/async-storage@3.0.2/packages/async-storage)

Updates `@rn-primitives/portal` from 1.3.0 to 1.4.0

Updates `i18next` from 25.10.10 to 26.0.3
- [Release notes](https://github.com/i18next/i18next/releases)
- [Changelog](https://github.com/i18next/i18next/blob/master/CHANGELOG.md)
- [Commits](i18next/i18next@v25.10.10...v26.0.3)

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

Updates `react` from 19.2.0 to 19.2.4
- [Release notes](https://github.com/facebook/react/releases)
- [Changelog](https://github.com/facebook/react/blob/main/CHANGELOG.md)
- [Commits](https://github.com/facebook/react/commits/v19.2.4/packages/react)

Updates `react-dom` from 19.2.0 to 19.2.4
- [Release notes](https://github.com/facebook/react/releases)
- [Changelog](https://github.com/facebook/react/blob/main/CHANGELOG.md)
- [Commits](https://github.com/facebook/react/commits/v19.2.4/packages/react-dom)

Updates `react-i18next` from 16.6.6 to 17.0.2
- [Changelog](https://github.com/i18next/react-i18next/blob/master/CHANGELOG.md)
- [Commits](i18next/react-i18next@v16.6.6...v17.0.2)

Updates `react-native` from 0.83.2 to 0.84.1
- [Release notes](https://github.com/facebook/react-native/releases)
- [Changelog](https://github.com/facebook/react-native/blob/main/CHANGELOG.md)
- [Commits](https://github.com/facebook/react-native/commits/v0.84.1/packages/react-native)

Updates `react-native-reanimated` from 4.2.1 to 4.3.0
- [Release notes](https://github.com/software-mansion/react-native-reanimated/releases)
- [Changelog](https://github.com/software-mansion/react-native-reanimated/blob/main/packages/react-native-reanimated/RELEASE.md)
- [Commits](https://github.com/software-mansion/react-native-reanimated/commits/4.3.0/packages/react-native-reanimated)

Updates `react-native-safe-area-context` from 5.6.2 to 5.7.0
- [Release notes](https://github.com/AppAndFlow/react-native-safe-area-context/releases)
- [Commits](AppAndFlow/react-native-safe-area-context@v5.6.2...v5.7.0)

Updates `react-native-screens` from 4.23.0 to 4.24.0
- [Release notes](https://github.com/software-mansion/react-native-screens/releases)
- [Commits](software-mansion/react-native-screens@4.23.0...4.24.0)

Updates `react-native-svg` from 15.15.3 to 15.15.4
- [Release notes](https://github.com/react-native-community/react-native-svg/releases)
- [Commits](software-mansion/react-native-svg@v15.15.3...v15.15.4)

Updates `react-native-worklets` from 0.7.2 to 0.8.1
- [Release notes](https://github.com/software-mansion/react-native-reanimated/releases)
- [Commits](https://github.com/software-mansion/react-native-reanimated/commits/worklets-0.8.1/packages/react-native-worklets)

Updates `tailwindcss` from 3.4.19 to 4.2.2
- [Release notes](https://github.com/tailwindlabs/tailwindcss/releases)
- [Changelog](https://github.com/tailwindlabs/tailwindcss/blob/main/CHANGELOG.md)
- [Commits](https://github.com/tailwindlabs/tailwindcss/commits/v4.2.2/packages/tailwindcss)

Updates `typescript` from 5.9.3 to 6.0.2
- [Release notes](https://github.com/microsoft/TypeScript/releases)
- [Commits](microsoft/TypeScript@v5.9.3...v6.0.2)

---
updated-dependencies:
- dependency-name: "@react-native-async-storage/async-storage"
  dependency-version: 3.0.2
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dependencies
- dependency-name: "@rn-primitives/portal"
  dependency-version: 1.4.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: i18next
  dependency-version: 26.0.3
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dependencies
- dependency-name: lucide-react-native
  dependency-version: 1.7.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dependencies
- dependency-name: react
  dependency-version: 19.2.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: react-dom
  dependency-version: 19.2.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: react-i18next
  dependency-version: 17.0.2
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dependencies
- dependency-name: react-native
  dependency-version: 0.84.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: react-native-reanimated
  dependency-version: 4.3.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: react-native-safe-area-context
  dependency-version: 5.7.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: react-native-screens
  dependency-version: 4.24.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: react-native-svg
  dependency-version: 15.15.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: react-native-worklets
  dependency-version: 0.8.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: tailwindcss
  dependency-version: 4.2.2
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dependencies
- dependency-name: typescript
  dependency-version: 6.0.2
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot bot commented on behalf of github Apr 1, 2026

Assignees

The following users could not be added as assignees: victorzarzar. Either the username does not exist or it does not have the correct permissions to be added as an assignee.

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

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

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants