Skip to content

fix(deps)(deps): bump the dependencies group across 1 directory with 17 updates - #1855

Merged
github-actions[bot] merged 1 commit into
mainfrom
dependabot/npm_and_yarn/dependencies-05f0c098e9
Oct 19, 2026
Merged

fix(deps)(deps): bump the dependencies group across 1 directory with 17 updates#1855
github-actions[bot] merged 1 commit into
mainfrom
dependabot/npm_and_yarn/dependencies-05f0c098e9

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 19, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

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

Package From To
@graphql-tools/schema 10.1.4 10.1.5
expo-application 58.1.1 58.1.2
expo-dev-client 58.0.13 58.0.14
expo-haptics 58.0.6 58.0.7
expo-image 58.0.14 58.0.15
expo-notifications 58.1.3 58.1.5
i18next 26.4.4 26.4.7
react 19.3.0 19.3.1
react-i18next 17.0.16 17.0.20
react-native 0.87.1 0.88.0
react-native-svg 15.15.5 15.16.0
@expo/cli 58.1.7 58.1.11
@react-native/jest-preset 0.87.1 0.88.0
react-test-renderer 19.3.0 19.3.1
ts-jest 29.4.14 29.4.15
@vitest/coverage-v8 5.0.4 5.0.5
vitest 5.0.4 5.0.5

Updates @graphql-tools/schema from 10.1.4 to 10.1.5

Changelog

Sourced from @​graphql-tools/schema's changelog.

10.1.5

Patch Changes

  • #8445 82457d1 Thanks @​ardatan! - dependencies updates:

  • #8445 82457d1 Thanks @​ardatan! - Fix: Preserve symbol-keyed GraphQL extensions when building, merging, or extracting schemas.

    GraphQL.js v17 allows string | symbol keys on schema/type/field extensions (via toObjMapWithSymbols). @graphql-tools was dropping those symbol keys in two places:

    1. mergeDeep only walked enumerable string keys (for...in), so symbol extensions were lost when applying schemaExtensions.
    2. extractExtensionsFromSchema did not copy non-enumerable own symbol keys (enumerable symbols already survive object rest/spread; the explicit loop covers the non-enumerable case).

    Example (bug)

    import { makeExecutableSchema } from '@graphql-tools/schema'
const META = Symbol('META')
const schema = makeExecutableSchema({
typeDefs: /* GraphQL */ type Query { hello: String },
schemaExtensions: {
schemaExtensions: {
[META]: { source: 'app' },
tagged: true,
},
types: {},
},
})
// Before: only string keys survived
// schema.extensions === { tagged: true }
// After: symbol keys are preserved
// schema.extensions[META] === { source: 'app' }
// schema.extensions.tagged === true

    Schema extension merge/extract and resolver merging always enable { enumerable: true, nonEnumerable: true } so symbol keys survive in tools' own merge/extract paths on every supported GraphQL.js major. (GraphQL.js itself may still drop symbol keys from field configs below v17 when rebuilding types.)

    mergeDeep API

    mergeDeep now accepts an options object. The old positional boolean arguments still work but are deprecated.

... (truncated)

Commits

Updates expo-application from 58.1.1 to 58.1.2

Release notes

Sourced from expo-application's releases.

expo-application@58.1.2

Patch Changes

  • [Android] Fix async functions rejecting with NoSuchMethodError on expo-modules-core 58.0.18 and later. The prebuilt Android library is now built against Expo Modules v2 runtime 0.2.5. (#51693 by @​alanjhughes)
Changelog

Sourced from expo-application's changelog.

58.1.2

Patch Changes

  • [Android] Fix async functions rejecting with NoSuchMethodError on expo-modules-core 58.0.18 and later. The prebuilt Android library is now built against Expo Modules v2 runtime 0.2.5. (#51693 by @​alanjhughes)
Commits

Updates expo-dev-client from 58.0.13 to 58.0.14

Release notes

Sourced from expo-dev-client's releases.

expo-dev-client@58.0.14

Patch Changes

  • Updated dependencies.
    • expo-dev-launcher@58.0.14
Changelog

Sourced from expo-dev-client's changelog.

58.0.14

Patch Changes

  • Updated dependencies.
    • expo-dev-launcher@58.0.14
Commits

Updates expo-haptics from 58.0.6 to 58.0.7

Release notes

Sourced from expo-haptics's releases.

expo-haptics@58.0.7

Patch Changes

  • [Android] Fix async functions rejecting with NoSuchMethodError on expo-modules-core 58.0.18 and later. The prebuilt Android library is now built against Expo Modules v2 runtime 0.2.5. (#51693 by @​alanjhughes)
Changelog

Sourced from expo-haptics's changelog.

58.0.7

Patch Changes

  • [Android] Fix async functions rejecting with NoSuchMethodError on expo-modules-core 58.0.18 and later. The prebuilt Android library is now built against Expo Modules v2 runtime 0.2.5. (#51693 by @​alanjhughes)
Commits

Updates expo-image from 58.0.14 to 58.0.15

Release notes

Sourced from expo-image's releases.

expo-image-manipulator@58.0.15

Patch Changes

  • Bump precompiled artifacts due to ABI breakage in expo-modules-core@58.0.23. (#51823 by @​alanjhughes)
Changelog

Sourced from expo-image's changelog.

58.0.15

Patch Changes

  • Use AssetRegistry from public API instead of Metro entry point. (#51302 by @​byCedric)
Commits

Updates expo-notifications from 58.1.3 to 58.1.5

Release notes

Sourced from expo-notifications's releases.

expo-notifications@58.1.5

Patch Changes

  • Updated dependencies. (#51693)
    • expo-application@58.1.2
Changelog

Sourced from expo-notifications's changelog.

58.1.5

Patch Changes

  • Updated dependencies. (#51693)
    • expo-application@58.1.2

58.1.4

Patch Changes

  • Updated dependencies.
    • @​expo/image-utils@​0.12.5
    • expo-constants@58.0.12
Commits

Updates i18next from 26.4.4 to 26.4.7

Release notes

Sourced from i18next's releases.

v26.4.7

  • perf: cloneInstance() no longer inherits preload. loadResources() adds every preload language to each load, and clones copied preload from the parent, so a clone's init() and every changeLanguage() walked all preloaded languages × all namespaces through queueLoad() / hasResourceBundle(), although the parent had already loaded them into the shared store. With i18next-http-middleware (one clone + changeLanguage() per request), 25 preloaded languages and 20 namespaces, that was most of the per-request CPU: the reproduction from the issue went from ~90 µs to ~10 µs per request, the same as with a single language. A clone now only loads what it uses itself: its changeLanguage() no longer waits for parent preload languages that are still loading (the parent's own init() still does), and clone.loadNamespaces() loads the new namespace for the clone's language and fallbacks instead of every preloaded language. clone.loadLanguages() works as before, the parent instance is unchanged, and passing preload to cloneInstance() keeps the old behavior. Thanks @​theMostCuriousHomunculus for the detailed report (#2451).

v26.4.6

  • fix: a fallback language whose formatted code is already in the hierarchy is no longer added a second time. toResolveHierarchy() checked the raw fallbackLng value against the list, but the list holds formatted codes, so any fallback written differently from its formatted form slipped through: lng: 'de-CH' with fallbackLng: 'de-ch' gave languages ['de-CH', 'de', 'de-CH'], and the same happened with fallbackLng: 'EN' + cleanCode, lowerCaseLng, and Intl aliases (iw-IL → he-IL). Missing keys were looked up in the same language twice. Only exact duplicates are removed; the order is unchanged. Thanks @​lprnmns (#2450).

v26.4.5

  • fix: hasLoadedNamespace(ns, { lng }) no longer stays false forever when the passed in lng is loaded under another code, or not at all. It checked the load state of the raw lng, but loadLanguages() stores a language under its resolved code (de-ch → de-CH, de-CH → de with load: 'languageOnly') and skips a lng outside supportedLngs entirely (only the fallback gets loaded), so that state never got set. react-i18next's useTranslation(ns, { lng }) then never became ready: with useSuspense it kept throwing an already resolved promise and React retried forever (100% CPU, SSR never finished), without it the load effect re-rendered in a loop. It now checks the code the language is actually loaded under, and for a lng outside supportedLngs only waits for the fallback, which is also what t() resolves to. Calls without lng and the precheck (react-i18next's bindI18n: 'languageChanging') are unchanged (react-i18next#1934).
Changelog

Sourced from i18next's changelog.

26.4.7

  • perf: cloneInstance() no longer inherits preload. loadResources() adds every preload language to each load, and clones copied preload from the parent, so a clone's init() and every changeLanguage() walked all preloaded languages × all namespaces through queueLoad() / hasResourceBundle(), although the parent had already loaded them into the shared store. With i18next-http-middleware (one clone + changeLanguage() per request), 25 preloaded languages and 20 namespaces, that was most of the per-request CPU: the reproduction from the issue went from ~90 µs to ~10 µs per request, the same as with a single language. A clone now only loads what it uses itself: its changeLanguage() no longer waits for parent preload languages that are still loading (the parent's own init() still does), and clone.loadNamespaces() loads the new namespace for the clone's language and fallbacks instead of every preloaded language. clone.loadLanguages() works as before, the parent instance is unchanged, and passing preload to cloneInstance() keeps the old behavior. Thanks @​theMostCuriousHomunculus for the detailed report (#2451).

26.4.6

  • fix: a fallback language whose formatted code is already in the hierarchy is no longer added a second time. toResolveHierarchy() checked the raw fallbackLng value against the list, but the list holds formatted codes, so any fallback written differently from its formatted form slipped through: lng: 'de-CH' with fallbackLng: 'de-ch' gave languages ['de-CH', 'de', 'de-CH'], and the same happened with fallbackLng: 'EN' + cleanCode, lowerCaseLng, and Intl aliases (iw-IL → he-IL). Missing keys were looked up in the same language twice. Only exact duplicates are removed; the order is unchanged. Thanks @​lprnmns (#2450).

26.4.5

  • fix: hasLoadedNamespace(ns, { lng }) no longer stays false forever when the passed in lng is loaded under another code, or not at all. It checked the load state of the raw lng, but loadLanguages() stores a language under its resolved code (de-ch → de-CH, de-CH → de with load: 'languageOnly') and skips a lng outside supportedLngs entirely (only the fallback gets loaded), so that state never got set. react-i18next's useTranslation(ns, { lng }) then never became ready: with useSuspense it kept throwing an already resolved promise and React retried forever (100% CPU, SSR never finished), without it the load effect re-rendered in a loop. It now checks the code the language is actually loaded under, and for a lng outside supportedLngs only waits for the fallback, which is also what t() resolves to. Calls without lng and the precheck (react-i18next's bindI18n: 'languageChanging') are unchanged (react-i18next#1934).
Commits

Updates react from 19.3.0 to 19.3.1

Release notes

Sourced from react's releases.

19.3.1 (October 14th, 2026)

React Server Components

Commits

Updates react-i18next from 17.0.16 to 17.0.20

Changelog

Sourced from react-i18next's changelog.

17.0.20

  • fix: useTranslation no longer suspends when a missing namespace is loaded by a synchronous backend. With useSuspense (the default), a namespace that wasn't in the store yet always made the component throw the loading promise, even when the backend had already delivered the resources while that promise was being created. React then showed the Suspense fallback and rendered again right away, which appears as a fallback flash (a white flash in React Native) and costs performance. The hook now starts the load first, checks the store again and only suspends if the namespace is still missing. This helps every backend that calls back synchronously, for example i18next-resources-to-backend with a static resources object or a loader that returns the data directly. Async backends, and an instance that isn't initialized yet, still suspend as before. Thanks @​oblador (#1937).

17.0.19

  • fix: useTranslation with an inline selector keyPrefix (useTranslation('ns', { keyPrefix: ($) => $.role })) returned a new t on every render, so every effect, useCallback and useMemo depending on t ran again each time. The cached t was compared against the keyPrefix function itself, and an inline arrow is a new function on every render. It is now compared against the key the selector resolves to (with the same options and namespace list getFixedT resolves it with), so t keeps its identity as long as the resolved prefix does, just like a string keyPrefix. A selector that resolves to a different key still gets a new t, and i18next still resolves the selector on each t call as before. Fixes #1936.
  • fix: useTranslation kept returning the previous t when only the namespace (useTranslation('a') → useTranslation('b')) or only the i18n instance (another instance with the same language, via props or I18nextProvider) changed on a mounted component. That t kept resolving against the old namespace or instance until something else (the language, the ready state, a bound i18n event) produced a new one. Both are now part of the check that decides whether the cached t can be reused.

17.0.18

  • fix(Trans): with shouldUnescape, the default unescape now turns   and &[#160](https://github.com/i18next/react-i18next/issues/160); into a no-break space (U+00A0) instead of a regular space (U+0020). The regular space dropped what the entity is for: u nás or 10 km could wrap across lines, and consecutive  s collapsed into one space. This also matches IcuTrans, whose entity decoder already mapped   to U+00A0. Compatibility note: only affects shouldUnescape; snapshots or exact textContent comparisons of such text now contain U+00A0 (Testing Library's default normalizer still matches it as a space). A custom react.unescape function can restore the old mapping for text nodes. Thanks @​lprnmns (#1935).

17.0.17

  • perf: useTranslation no longer unsubscribes and resubscribes its i18n listeners on every render. The subscribe callback handed to useSyncExternalStore depended on the merged options object, which is rebuilt whenever props is a new object: with no options (the {} default), with options passed inline (useTranslation('ns', { keyPrefix })), and through withTranslation and <Translation>. A new subscribe makes React resubscribe, so each render of each caller ran i18n.off and i18n.on in an extra effect. It now depends only on the instance and the bindI18n/bindI18nStore event names. No updates were ever missed, because React re-checks the snapshot after resubscribing; this only removes the churn, which adds up with many mounted components that re-render often. Reported via next-i18next#2349.
Commits

Updates react-native from 0.87.1 to 0.88.0

Release notes

Sourced from react-native's releases.

0.88.0

Added

  • C++: Add <React/FeatureFlags.h> umbrella header as the public entry point for react/featureflags (f970054a8a by @​j-piasecki)
  • C++: Add <React/RendererBridging.h> umbrella header as the public entry point for react/renderer/bridging (5b680c5f9f by @​j-piasecki)
  • C++: Add <React/Timing.h> umbrella header as the public entry point for react/timing (70f172d29f by @​j-piasecki)
  • C++: Added missing mutex include in HostTarget.h (3f8f5c216a by @​etodanik)
  • EventTarget: Enable the imperative EventTarget API (addEventListener, removeEventListener, dispatchEvent) on native view refs in canary (8480b86820 by @​rubennorte)
  • Feature Flags: Add enableImageTransparentTintColor feature flag (c5bd054983 by @​coado)
  • JavaScript API: Deprecate 'react-native/Libraries/Core/InitializeCore'. Use 'react-native/setup-env' instead. (554baba159 by @​huntie)
  • PlatformColor: Support a lazy raw color fallback for PlatformColor when native tokens fail to resolve (65008fcdd0 by @​Abbondanzo)
  • React Native DevTools: Experimental performance screenshots support and Page.captureScreenshot is added to the EXPERIMENTAL channel (4be68ef785 by @​huntie)
  • React Native DevTools: Support for inspecting WebSocket events in the Network panel is added to the CANARY channel (713ae6b1b9 by @​huntie)
  • React Native DevTools: Users and agents can now capture app screenshots via the Page.captureScreenshot command (00efc0a440 by @​huntie)
  • Text: Add object syntax for fontVariationSettings (376b99ff14 by @​evankatz14)
  • TypeScript: Add isInstalled() and clearAllLogs() to the LogBox TypeScript declarations (a69badd468 by @​Abbondanzo)
  • TypeScript: Add missing strictMode prop to FlatList TypeScript types (3e2403327c by @​drhops)
  • TypeScript: Add TypeScript declarations for requestIdleCallback and cancelIdleCallback (c086431a4b by @​Critteros)
  • VirtualizedList: Add missing ListItemComponent type to VirtualizedList props (5306e9229c by @​aravi365)

Android specific

  • Feature Flags: Add enableMountingCoordinatorPullModelAndroid feature flag (ece0efe837 by @​coado)
  • Network Inspection: Expose network event reporting to third-party networking stacks as an unstable API (83d0be8958 by @​huntie)
  • Networking: Send app name and version as the default User-Agent header for network requests, matching iOS (04e50d540d by Calvin Liu)
  • Renderer: Add inert Java plumbing (PullTransactionMountItem, FabricUIManager.onTransactionAvailable) for the pull model (6515647d94 by @​coado)
  • Renderer: Wire the pull-model mounting path in C++ behind enableMountingCoordinatorPullModelAndroid (9da1a01153 by @​coado)
  • Text: Add fontVariationSettings support for <Text> (19f7d144b9 by @​evankatz14)
  • TextInput: Add fontVariationSettings support for TextInput (a688608090 by @​evankatz14)
  • TurboModules: Add ArrayBuffer, the Java representation of a JS ArrayBuffer for TurboModules, with an explicit byte-ownership contract (5bb9639594 by Kamil Paradowski)
  • TurboModules: Add ArrayBuffer support to Java TurboModules (5fb3ebce1a by Kamil Paradowski)
  • TurboModules: Borrowed ArrayBuffer bytes are scoped to the synchronous call that received them. ArrayBuffer.bytes and ArrayBuffer.size throw IllegalStateException afterwards, and a ByteBuffer already obtained from bytes is unchecked and reads freed memory, so copy with ArrayBuffer.arrayBufferWithCopiedBytes to keep them (d84c13d511 by @​christophpurrer)

iOS specific

  • Text: Add fontVariationSettings support on iOS (8415753e21 by @​evankatz14)
  • Assets: Use asset catalog for ios images (26769a00b2 by @​janicduplessis)
  • CocoaPods: Add a React-cxxstableapi dependency to third-party New Architecture pods so they can resolve React Native's C++ API guard headers (d3daf111e0 by @​coado)
  • Legacy Architecture: Allow consumers to opt into RCT_REMOVE_LEGACY_MODULE_INTEROP and RCT_REMOVE_LEGACY_COMPONENT_INTEROP from CocoaPods and SwiftPM. Both default to off and will become the default in a future release (b933d18177 by @​christophpurrer)
  • SceneDelegate: Add SceneDelegate lifecycle support (7bfe32fd33 by @​artus9033)
  • Styles: Print warning advice when using shadow* styles without providing a solid background color (eb4d3892ab by @​hannojg)

Changed

... (truncated)

Changelog

Sourced from react-native's changelog.

v0.88.0

Added

  • C++: Add <React/FeatureFlags.h> umbrella header as the public entry point for react/featureflags (f970054a8a by @​j-piasecki)
  • C++: Add <React/RendererBridging.h> umbrella header as the public entry point for react/renderer/bridging (5b680c5f9f by @​j-piasecki)
  • C++: Add <React/Timing.h> umbrella header as the public entry point for react/timing (70f172d29f by @​j-piasecki)
  • C++: Added missing mutex include in HostTarget.h (3f8f5c216a by @​etodanik)
  • EventTarget: Enable the imperative EventTarget API (addEventListener, removeEventListener, dispatchEvent) on native view refs in canary (8480b86820 by @​rubennorte)
  • Feature Flags: Add enableImageTransparentTintColor feature flag (c5bd054983 by @​coado)
  • JavaScript API: Deprecate 'react-native/Libraries/Core/InitializeCore'. Use 'react-native/setup-env' instead. (554baba159 by @​huntie)
  • PlatformColor: Support a lazy raw color fallback for PlatformColor when native tokens fail to resolve (65008fcdd0 by @​Abbondanzo)
  • React Native DevTools: Experimental performance screenshots support and Page.captureScreenshot is added to the EXPERIMENTAL channel (4be68ef785 by @​huntie)
  • React Native DevTools: Support for inspecting WebSocket events in the Network panel is added to the CANARY channel (713ae6b1b9 by @​huntie)
  • React Native DevTools: Users and agents can now capture app screenshots via the Page.captureScreenshot command (00efc0a440 by @​huntie)
  • Text: Add object syntax for fontVariationSettings (376b99ff14 by @​evankatz14)
  • TypeScript: Add isInstalled() and clearAllLogs() to the LogBox TypeScript declarations (a69badd468 by @​Abbondanzo)
  • TypeScript: Add missing strictMode prop to FlatList TypeScript types (3e2403327c by @​drhops)
  • TypeScript: Add TypeScript declarations for requestIdleCallback and cancelIdleCallback (c086431a4b by @​Critteros)
  • VirtualizedList: Add missing ListItemComponent type to VirtualizedList props (5306e9229c by @​aravi365)

Android specific

  • Feature Flags: Add enableMountingCoordinatorPullModelAndroid feature flag (ece0efe837 by @​coado)
  • Network Inspection: Expose network event reporting to third-party networking stacks as an unstable API (83d0be8958 by @​huntie)
  • Networking: Send app name and version as the default User-Agent header for network requests, matching iOS (04e50d540d by Calvin Liu)
  • Renderer: Add inert Java plumbing (PullTransactionMountItem, FabricUIManager.onTransactionAvailable) for the pull model (6515647d94 by @​coado)
  • Renderer: Wire the pull-model mounting path in C++ behind enableMountingCoordinatorPullModelAndroid (9da1a01153 by @​coado)
  • Text: Add fontVariationSettings support for <Text> (19f7d144b9 by @​evankatz14)
  • TextInput: Add fontVariationSettings support for TextInput (a688608090 by @​evankatz14)
  • TurboModules: Add ArrayBuffer, the Java representation of a JS ArrayBuffer for TurboModules, with an explicit byte-ownership contract (5bb9639594 by Kamil Paradowski)
  • TurboModules: Add ArrayBuffer support to Java TurboModules (5fb3ebce1a by Kamil Paradowski)
  • TurboModules: Borrowed ArrayBuffer bytes are scoped to the synchronous call that received them. ArrayBuffer.bytes and ArrayBuffer.size throw IllegalStateException afterwards, and a ByteBuffer already obtained from bytes is unchecked and reads freed memory, so copy with ArrayBuffer.arrayBufferWithCopiedBytes to keep them (d84c13d511 by @​christophpurrer)

iOS specific

  • Text: Add fontVariationSettings support on iOS (8415753e21 by @​evankatz14)
  • Assets: Use asset catalog for ios images (26769a00b2 by @​janicduplessis)
  • CocoaPods: Add a React-cxxstableapi dependency to third-party New Architecture pods so they can resolve React Native's C++ API guard headers (d3daf111e0 by @​coado)
  • Legacy Architecture: Allow consumers to opt into RCT_REMOVE_LEGACY_MODULE_INTEROP and RCT_REMOVE_LEGACY_COMPONENT_INTEROP from CocoaPods and SwiftPM. Both default to off and will become the default in a future release (b933d18177 by @​christophpurrer)
  • SceneDelegate: Add SceneDelegate lifecycle support (7bfe32fd33 by @​artus9033)
  • Styles: Print warning advice when using shadow* styles without providing a solid background color (eb4d3892ab by @​hannojg)

Changed

... (truncated)

Commits

Updates react-native-svg from 15.15.5 to 15.16.0

Release notes

Sourced from react-native-svg's releases.

v15.16.0

What's Changed

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file security Security related issue labels Oct 19, 2026
@dependabot
fix(deps)(deps): bump the dependencies group across 1 directory with …
c93231e 
…17 updates

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

| Package | From | To |
| --- | --- | --- |
| [@graphql-tools/schema](https://github.com/ardatan/graphql-tools/tree/HEAD/packages/schema) | `10.1.4` | `10.1.5` |
| [expo-application](https://github.com/expo/expo/tree/HEAD/packages/expo-application) | `58.1.1` | `58.1.2` |
| [expo-dev-client](https://github.com/expo/expo/tree/HEAD/packages/expo-dev-client) | `58.0.13` | `58.0.14` |
| [expo-haptics](https://github.com/expo/expo/tree/HEAD/packages/expo-haptics) | `58.0.6` | `58.0.7` |
| [expo-image](https://github.com/expo/expo/tree/HEAD/packages/expo-image) | `58.0.14` | `58.0.15` |
| [expo-notifications](https://github.com/expo/expo/tree/HEAD/packages/expo-notifications) | `58.1.3` | `58.1.5` |
| [i18next](https://github.com/i18next/i18next) | `26.4.4` | `26.4.7` |
| [react](https://github.com/react/react/tree/HEAD/packages/react) | `19.3.0` | `19.3.1` |
| [react-i18next](https://github.com/i18next/react-i18next) | `17.0.16` | `17.0.20` |
| [react-native](https://github.com/react/react-native/tree/HEAD/packages/react-native) | `0.87.1` | `0.88.0` |
| [react-native-svg](https://github.com/software-mansion/react-native-svg) | `15.15.5` | `15.16.0` |
| [@expo/cli](https://github.com/expo/expo/tree/HEAD/packages/@expo/cli) | `58.1.7` | `58.1.11` |
| [@react-native/jest-preset](https://github.com/react/react-native/tree/HEAD/packages/jest-preset) | `0.87.1` | `0.88.0` |
| [react-test-renderer](https://github.com/react/react/tree/HEAD/packages/react-test-renderer) | `19.3.0` | `19.3.1` |
| [ts-jest](https://github.com/kulshekhar/ts-jest) | `29.4.14` | `29.4.15` |
| [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) | `5.0.4` | `5.0.5` |
| [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `5.0.4` | `5.0.5` |



Updates `@graphql-tools/schema` from 10.1.4 to 10.1.5
- [Release notes](https://github.com/ardatan/graphql-tools/releases)
- [Changelog](https://github.com/ardatan/graphql-tools/blob/master/packages/schema/CHANGELOG.md)
- [Commits](https://github.com/ardatan/graphql-tools/commits/@graphql-tools/schema@10.1.5/packages/schema)

Updates `expo-application` from 58.1.1 to 58.1.2
- [Release notes](https://github.com/expo/expo/releases)
- [Changelog](https://github.com/expo/expo/blob/main/packages/expo-application/CHANGELOG.md)
- [Commits](https://github.com/expo/expo/commits/expo-application@58.1.2/packages/expo-application)

Updates `expo-dev-client` from 58.0.13 to 58.0.14
- [Release notes](https://github.com/expo/expo/releases)
- [Changelog](https://github.com/expo/expo/blob/main/packages/expo-dev-client/CHANGELOG.md)
- [Commits](https://github.com/expo/expo/commits/expo-dev-client@58.0.14/packages/expo-dev-client)

Updates `expo-haptics` from 58.0.6 to 58.0.7
- [Release notes](https://github.com/expo/expo/releases)
- [Changelog](https://github.com/expo/expo/blob/main/packages/expo-haptics/CHANGELOG.md)
- [Commits](https://github.com/expo/expo/commits/expo-haptics@58.0.7/packages/expo-haptics)

Updates `expo-image` from 58.0.14 to 58.0.15
- [Release notes](https://github.com/expo/expo/releases)
- [Changelog](https://github.com/expo/expo/blob/main/packages/expo-image/CHANGELOG.md)
- [Commits](https://github.com/expo/expo/commits/expo-image@58.0.15/packages/expo-image)

Updates `expo-notifications` from 58.1.3 to 58.1.5
- [Release notes](https://github.com/expo/expo/releases)
- [Changelog](https://github.com/expo/expo/blob/main/packages/expo-notifications/CHANGELOG.md)
- [Commits](https://github.com/expo/expo/commits/expo-notifications@58.1.5/packages/expo-notifications)

Updates `i18next` from 26.4.4 to 26.4.7
- [Release notes](https://github.com/i18next/i18next/releases)
- [Changelog](https://github.com/i18next/i18next/blob/master/CHANGELOG.md)
- [Commits](i18next/i18next@v26.4.4...v26.4.7)

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

Updates `react-i18next` from 17.0.16 to 17.0.20
- [Changelog](https://github.com/i18next/react-i18next/blob/master/CHANGELOG.md)
- [Commits](i18next/react-i18next@v17.0.16...v17.0.20)

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

Updates `react-native-svg` from 15.15.5 to 15.16.0
- [Release notes](https://github.com/software-mansion/react-native-svg/releases)
- [Commits](software-mansion/react-native-svg@v15.15.5...v15.16.0)

Updates `@expo/cli` from 58.1.7 to 58.1.11
- [Release notes](https://github.com/expo/expo/releases)
- [Changelog](https://github.com/expo/expo/blob/main/packages/@expo/cli/CHANGELOG.md)
- [Commits](https://github.com/expo/expo/commits/@expo/cli@58.1.11/packages/@expo/cli)

Updates `@react-native/jest-preset` from 0.87.1 to 0.88.0
- [Release notes](https://github.com/react/react-native/releases)
- [Changelog](https://github.com/react/react-native/blob/main/CHANGELOG.md)
- [Commits](https://github.com/react/react-native/commits/v0.88.0/packages/jest-preset)

Updates `react-test-renderer` from 19.3.0 to 19.3.1
- [Release notes](https://github.com/react/react/releases)
- [Changelog](https://github.com/react/react/blob/main/CHANGELOG.md)
- [Commits](https://github.com/react/react/commits/v19.3.1/packages/react-test-renderer)

Updates `ts-jest` from 29.4.14 to 29.4.15
- [Release notes](https://github.com/kulshekhar/ts-jest/releases)
- [Changelog](https://github.com/kulshekhar/ts-jest/blob/main/CHANGELOG.md)
- [Commits](kulshekhar/ts-jest@v29.4.14...v29.4.15)

Updates `@vitest/coverage-v8` from 5.0.4 to 5.0.5
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md)
- [Commits](https://github.com/vitest-dev/vitest/commits/v5.0.5/packages/coverage-v8)

Updates `vitest` from 5.0.4 to 5.0.5
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md)
- [Commits](https://github.com/vitest-dev/vitest/commits/v5.0.5/packages/vitest)

---
updated-dependencies:
- dependency-name: "@expo/cli"
  dependency-version: 58.1.11
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: "@graphql-tools/schema"
  dependency-version: 10.1.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: "@react-native/jest-preset"
  dependency-version: 0.88.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: "@vitest/coverage-v8"
  dependency-version: 5.0.5
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: expo-application
  dependency-version: 58.1.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: expo-dev-client
  dependency-version: 58.0.14
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: expo-haptics
  dependency-version: 58.0.7
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: expo-image
  dependency-version: 58.0.15
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: expo-notifications
  dependency-version: 58.1.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: i18next
  dependency-version: 26.4.7
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: react
  dependency-version: 19.3.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: react-i18next
  dependency-version: 17.0.20
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: react-native
  dependency-version: 0.88.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: react-native-svg
  dependency-version: 15.16.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: react-test-renderer
  dependency-version: 19.3.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: ts-jest
  dependency-version: 29.4.15
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: vitest
  dependency-version: 5.0.5
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title fix(deps)(deps): bump the dependencies group with 17 updates fix(deps)(deps): bump the dependencies group across 1 directory with 17 updates Oct 19, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/dependencies-05f0c098e9 branch from 661050f to c93231e Compare October 19, 2026 21:49
@github-actions
github-actions Bot merged commit 4b7d7e5 into main Oct 19, 2026
10 of 30 checks passed
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/dependencies-05f0c098e9 branch October 19, 2026 21:49
@dependabot
dependabot Bot deployed to security-review October 19, 2026 21:52 Active

This branch was successfully deployed

1 active deployment
security-review — c93231e3 Deployed Oct 19, 2026 by dependabot[bot] via Security Dashboard #1411
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file security Security related issue

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants