Skip to content

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

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/dependencies-9fd5269490
Open

fix(deps)(deps): bump the dependencies group across 1 directory with 18 updates#893
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/dependencies-9fd5269490

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 3, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

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

Package From To
@shopify/flash-list 2.3.1 2.3.2
@walletconnect/react-native-compat 2.23.9 2.23.10
@walletconnect/utils 2.23.9 2.23.10
i18next 26.3.0 26.3.6
react 19.2.5 19.2.8
@types/react 19.2.16 19.2.18
react-i18next 17.0.8 17.0.11
react-native-safe-area-context 5.7.0 5.8.0
react-native-screens 4.24.0 4.26.2
react-native-svg 15.15.4 15.15.5
@react-native-community/cli 20.1.3 20.2.0
@react-native/jest-preset 0.85.2 0.86.2
@types/react-dom 19.2.3 19.2.4
detox 20.51.3 20.51.4
prettier 3.8.3 3.9.6
react-test-renderer 19.2.7 19.2.8
ts-jest 29.4.11 29.4.12

Updates @shopify/flash-list from 2.3.1 to 2.3.2

Release notes

Sourced from @​shopify/flash-list's releases.

v2.3.2

What's Changed

New Contributors

Full Changelog: Shopify/flash-list@v2.3.1...v2.3.2

Commits
  • 8c1375e v2.3.2
  • d6c9513 feat(sticky-headers): configure sticky header zIndex (#2311)
  • 8ca7477 fix: scroll to index autoscroll race (#2290)
  • f4278ba Update skill to include fixture checks
  • 8bf4c81 chore(deps): bump picomatch from 2.3.1 to 2.3.2 in /fixture/web (#2210)
  • ea9956a chore(deps): bump picomatch from 2.3.1 to 2.3.2 (#2214)
  • 43ed94e chore(deps): bump picomatch from 2.3.1 to 2.3.2 in /documentation (#2212)
  • 508606e chore(deps): bump picomatch from 2.3.1 to 2.3.2 in /fixture/react-native (#2213)
  • f47a64e chore(skills): add analyze-feedback skill and incorporate agent learnings (#2...
  • 5ffed99 feat(skills): add analyze-feedback skill for agent workflow feedback (#2206)
  • Additional commits viewable in compare view

Updates @walletconnect/react-native-compat from 2.23.9 to 2.23.10

Release notes

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

@​walletconnect/react-native-compat@​2.23.10

Patch Changes

Changelog

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

2.23.10

Patch Changes

Commits
  • 3ef9f3e chore: update versions and lerna.json
  • 73b7d5c chore: update yttrium dependencies-wasm-0.10.57-kotlin-0.10.58
  • fcaaf3f chore: update yttrium dependencies-wasm-0.10.54-swift-0.10.54-kotlin-0.10.55
  • See full diff in compare view

Updates @walletconnect/utils from 2.23.9 to 2.23.10

Release notes

Sourced from @​walletconnect/utils's releases.

@​walletconnect/utils@​2.23.10

Patch Changes

  • #7252 cd32ff1 Thanks @​ganchoradkov! - Add TVF extraction for Canton's canton_prepareSignExecute.

  • #7247 3ea740e Thanks @​ganchoradkov! - Reject SIWE/CAIP-122 statements containing line breaks in formatMessage. Per EIP-4361 the statement is a single line, and embedded \r/\n (from a caller-supplied statement or untrusted recap-derived text) could forge other fields (URI, Nonce, etc.) in the signed message. The check runs on the final statement after recap formatting, and validateSignedCacao now returns false for such malformed payloads instead of throwing.

  • Updated dependencies [63ff999]:

    • @​walletconnect/types@​2.23.10
Changelog

Sourced from @​walletconnect/utils's changelog.

2.23.10

Patch Changes

  • #7252 cd32ff1 Thanks @​ganchoradkov! - Add TVF extraction for Canton's canton_prepareSignExecute.

  • #7247 3ea740e Thanks @​ganchoradkov! - Reject SIWE/CAIP-122 statements containing line breaks in formatMessage. Per EIP-4361 the statement is a single line, and embedded \r/\n (from a caller-supplied statement or untrusted recap-derived text) could forge other fields (URI, Nonce, etc.) in the signed message. The check runs on the final statement after recap formatting, and validateSignedCacao now returns false for such malformed payloads instead of throwing.

  • Updated dependencies [63ff999]:

    • @​walletconnect/types@​2.23.10
Commits
  • 3ef9f3e chore: update versions and lerna.json
  • cd32ff1 feat: add TVF extraction for Canton canton_prepareSignExecute
  • 8857209 fix: validate statement after recap formatting; soften validateSignedCacao
  • 3ea740e fix: reject SIWE statements containing line breaks per EIP-4361
  • See full diff in compare view

Updates i18next from 26.3.0 to 26.3.6

Release notes

Sourced from i18next's releases.

v26.3.6

  • fix: allow TypeScript 7 in the optional typescript peer dependency range (^5 || ^6 || ^7). With typescript@7.0.2 in a project, npm install failed with an ERESOLVE peer conflict. The published types are TS7-compatible as-is: every test/typescript suite produces identical results under 6.0 and 7.0.2. Reported in react-i18next#1927, thanks @​andikapradanaarif.

v26.3.5

  • fix: $t() nesting options blocks that span multiple lines are now parsed. nest() decided where the nested key ends by testing match[1] with /{.*}/, whose dot does not cross line breaks — so a $t(key, { ... }) options object containing a newline was treated as having no options, mis-split as formatters, and the nested lookup ran without its options (placeholders stayed unresolved). The nesting regexp itself already matches newlines inside $t(...); adding the s (dotAll) flag makes multiline options behave like the single-line form. Thanks @​spokodev (#2440).
  • fix: getUsedParamsDetails (the returnDetails: true path) no longer mutates the passed replace object. It wrote count straight onto options.replace so the returned usedParams would include it — a caller reusing one replace object across t() calls then carried a stale count into later interpolations (e.g. a previous call's count: 5 rendered instead of the current call's value). The details are now built from a copy; usedParams still includes count. Thanks @​spokodev (#2441).
  • fix: with the default skipOnVariables: true + escapeValue: true, a {{placeholder}} carried inside an interpolated value now stays literal even when the value contains escapable characters. The skip logic advanced the regex lastIndex by the raw value length, but the escaped text written into the string is longer, so lastIndex landed inside the inserted value and a trailing {{placeholder}} in it got interpolated — leaking another in-scope variable that should have stayed literal (values without escapable characters were already skipped correctly). The advance now uses the escaped length that is actually written, and the regex-safe $-doubling is applied only at the String.replace call so it can't distort the length arithmetic. Thanks @​spokodev (#2442).

v26.3.4

  • fix(security): deepExtend (used by addResourceBundle(..., deep, overwrite)) no longer recurses into inherited properties. It checked key existence with the in operator, which walks the prototype chain, so a source key matching an inherited built-in (e.g. hasOwnProperty, toString) caused recursion into the shared Object.prototype function and, with overwrite: true, could overwrite e.g. Object.prototype.hasOwnProperty.call with a non-callable value — corrupting a shared built-in process-wide (DoS). Existence is now checked with Object.prototype.hasOwnProperty.call, so such keys are copied as plain own data instead. This complements the existing __proto__/constructor guard and is also strictly more correct for an own-property merge. Only affects applications that pass attacker-controlled data with deep: true and overwrite: true; no standard backend/integration does this. Distinct from CVE-2026-48713 / CVE-2026-48714 (different packages, setPath mechanism). Thanks to zx (Jace) for the responsible disclosure.

v26.3.3

  • fix(types): selector t($ => $.arr, { returnObjects: true, context }) on a JSON array of heterogeneous objects now preserves each element's full shape (e.g. { transKey1: string; transKey2: string }[]) instead of collapsing to a union of partial element types. Two type-level causes: (1) FilterKeys evaluated the whole array element type at once, so keyof (A | B) only saw the keys common to every element — it now distributes over the object union and filters each element independently; (2) when TypeScript merges mismatched array element types it injects phantom optional undefined keys (e.g. transKey1_withContext?: undefined on elements that don't define it), which the context-detection helpers mistook for real context variants — they now skip keys typed as undefined. Also adds a dedicated context + returnObjects: true selector overload using const Fn + ReturnType<Fn>, so Target is no longer collapsed to unknown via ApplyTarget. Resolves Problem 1 of #2398 (Problem 2 was already fixed on master). Thanks @​sauravgupta-dotcom (#2438). Fixes #2398.

v26.3.2

  • fix: chained formatters with a parenthesised option that contains the format separator (e.g. join(separator: ', ')) now work at any position in the chain, not just first. Previously the comma-in-parens reassembly only repaired formats[0], so {{v, uppercase, join(separator: ', ')}} split the join(...) option on the inner comma and never rejoined it, producing corrupt output. Replaced the first-position-only repair with a position-independent pass that re-joins fragments until each open paren closes. Thanks @​spokodev (#2437).

v26.3.1

  • fix(types): t() with a keyPrefix no longer pollutes its return type with sibling keys' values. A regression in 26.3.0 — the [Res] extends [never] guards added to KeysBuilderWithReturnObjects / KeysBuilderWithoutReturnObjects turned the builders into deferred conditional types, so KeyPrefix<Ns> stopped resolving to a literal union and keyPrefix inference widened to the whole namespace. Symptom: useTranslation(ns, { keyPrefix: 'a.b' }) then t('title') would resolve to '<a.b>.title' | '<other.path>.title' | ... instead of just the scoped value. Affected every react-i18next user using keyPrefix. Restored to the eager 26.2.0 form. The same-namespace conflict handling from #2434 still works via _DropConflictKeys at the merge layer (in options.d.ts). Thanks @​aaronrosenthal (#2436).
Changelog

Sourced from i18next's changelog.

26.3.6

  • fix: allow TypeScript 7 in the optional typescript peer dependency range (^5 || ^6 || ^7). With typescript@7.0.2 in a project, npm install failed with an ERESOLVE peer conflict. The published types are TS7-compatible as-is: every test/typescript suite produces identical results under 6.0 and 7.0.2. Reported in react-i18next#1927, thanks @​andikapradanaarif.

26.3.5

  • fix: $t() nesting options blocks that span multiple lines are now parsed. nest() decided where the nested key ends by testing match[1] with /{.*}/, whose dot does not cross line breaks — so a $t(key, { ... }) options object containing a newline was treated as having no options, mis-split as formatters, and the nested lookup ran without its options (placeholders stayed unresolved). The nesting regexp itself already matches newlines inside $t(...); adding the s (dotAll) flag makes multiline options behave like the single-line form. Thanks @​spokodev (#2440).
  • fix: getUsedParamsDetails (the returnDetails: true path) no longer mutates the passed replace object. It wrote count straight onto options.replace so the returned usedParams would include it — a caller reusing one replace object across t() calls then carried a stale count into later interpolations (e.g. a previous call's count: 5 rendered instead of the current call's value). The details are now built from a copy; usedParams still includes count. Thanks @​spokodev (#2441).
  • fix: with the default skipOnVariables: true + escapeValue: true, a {{placeholder}} carried inside an interpolated value now stays literal even when the value contains escapable characters. The skip logic advanced the regex lastIndex by the raw value length, but the escaped text written into the string is longer, so lastIndex landed inside the inserted value and a trailing {{placeholder}} in it got interpolated — leaking another in-scope variable that should have stayed literal (values without escapable characters were already skipped correctly). The advance now uses the escaped length that is actually written, and the regex-safe $-doubling is applied only at the String.replace call so it can't distort the length arithmetic. Thanks @​spokodev (#2442).

26.3.4

  • fix(security): deepExtend (used by addResourceBundle(..., deep, overwrite)) no longer recurses into inherited properties. It checked key existence with the in operator, which walks the prototype chain, so a source key matching an inherited built-in (e.g. hasOwnProperty, toString) caused recursion into the shared Object.prototype function and, with overwrite: true, could overwrite e.g. Object.prototype.hasOwnProperty.call with a non-callable value — corrupting a shared built-in process-wide (DoS). Existence is now checked with Object.prototype.hasOwnProperty.call, so such keys are copied as plain own data instead. This complements the existing __proto__/constructor guard and is also strictly more correct for an own-property merge. Only affects applications that pass attacker-controlled data with deep: true and overwrite: true; no standard backend/integration does this. Distinct from CVE-2026-48713 / CVE-2026-48714 (different packages, setPath mechanism). See advisory GHSA-6jcc-5g8w-32mx, CVSS 5.9 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H). Thanks to zx (Jace) @​manus-use for the responsible disclosure.

26.3.3

  • fix(types): selector t($ => $.arr, { returnObjects: true, context }) on a JSON array of heterogeneous objects now preserves each element's full shape (e.g. { transKey1: string; transKey2: string }[]) instead of collapsing to a union of partial element types. Two type-level causes: (1) FilterKeys evaluated the whole array element type at once, so keyof (A | B) only saw the keys common to every element — it now distributes over the object union and filters each element independently; (2) when TypeScript merges mismatched array element types it injects phantom optional undefined keys (e.g. transKey1_withContext?: undefined on elements that don't define it), which the context-detection helpers mistook for real context variants — they now skip keys typed as undefined. Also adds a dedicated context + returnObjects: true selector overload using const Fn + ReturnType<Fn>, so Target is no longer collapsed to unknown via ApplyTarget. Resolves Problem 1 of #2398 (Problem 2 was already fixed on master). Thanks @​sauravgupta-dotcom (#2438). Fixes #2398.

26.3.2

  • fix: chained formatters with a parenthesised option that contains the format separator (e.g. join(separator: ', ')) now work at any position in the chain, not just first. Previously the comma-in-parens reassembly only repaired formats[0], so {{v, uppercase, join(separator: ', ')}} split the join(...) option on the inner comma and never rejoined it, producing corrupt output. Replaced the first-position-only repair with a position-independent pass that re-joins fragments until each open paren closes. Thanks @​spokodev (#2437).

26.3.1

  • fix(types): t() with a keyPrefix no longer pollutes its return type with sibling keys' values. A regression in 26.3.0 — the [Res] extends [never] guards added to KeysBuilderWithReturnObjects / KeysBuilderWithoutReturnObjects turned the builders into deferred conditional types, so KeyPrefix<Ns> stopped resolving to a literal union and keyPrefix inference widened to the whole namespace. Symptom: useTranslation(ns, { keyPrefix: 'a.b' }) then t('title') would resolve to '<a.b>.title' | '<other.path>.title' | ... instead of just the scoped value. Affected every react-i18next user using keyPrefix. Restored to the eager 26.2.0 form. The same-namespace conflict handling from #2434 still works via _DropConflictKeys at the merge layer (in options.d.ts). Thanks @​aaronrosenthal (#2436).
Commits
  • e1c60d4 26.3.6
  • 04da43e fix: allow typescript 7 in optional peerDependencies range (react-i18next#1927)
  • 8eed4ac build
  • 573ae73 26.3.5
  • cc54b05 docs(changelog): 26.3.5 — multiline $t() options, replace mutation, escaped-l...
  • 3180d67 fix: skip interpolation of placeholders inside escaped values (#2442)
  • d16f5a2 fix: stop mutating the passed replace object when returning details (#2441)
  • bed56c1 fix: parse $t() nesting options block that spans multiple lines (#2440)
  • c19e458 docs(changelog): link GHSA advisory for deepExtend fix
  • 7bb87d0 docs(changelog): reference security advisory for deepExtend fix
  • Additional commits viewable in compare view

Updates react from 19.2.5 to 19.2.8

Release notes

Sourced from react's releases.

19.2.8 (July 21st, 2026)

React Server Components

19.2.7 (June 1st, 2026)

React Server Components

19.2.6 (May 6th, 2026)

React Server Components

Changelog

Sourced from react's changelog.

19.2.7 (June 1, 2026)

React Server Components

19.2.6 (May 6, 2026)

React Server Components

Commits
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for react since your current version.


Updates @types/react from 19.2.16 to 19.2.18

Commits

Updates react-i18next from 17.0.8 to 17.0.11

Changelog

Sourced from react-i18next's changelog.

17.0.11

  • chore: html-parse-stringify updated to ^4.0.1. The parser powering <Trans> is now actively maintained under the i18next org (i18next/html-parse-stringify) after years without upstream releases. 4.x brings modern dual ESM/CJS packaging with an exports map, zero runtime dependencies, reworked TypeScript types and a long list of parser fixes (literal < in text, multiline/CRLF attribute values, comments containing >, doctype handling, quote-aware bracket handling).
  • refactor(Trans): the internal escapeLiteralLessThan scanner (~80 lines) is replaced by the parser's new allowedTags option with identical semantics: only numbered tags, kept basic HTML tags and known component names are parsed as markup, any other tag-shaped sequence in the translation stays literal text. Rendered output is unchanged (all 493 tests pass, including the #1880 and #1893 escaping cases).

17.0.10

  • fix(warnings): the useTranslation and Trans "You will need to pass in an i18next instance" warnings now match the useSSR wording, mentioning the props/context alternatives and the most common unexplained cause at scale: duplicate react-i18next copies in monorepo setups. The Trans variant also referenced the internal i18nextReactModule name; it now points to the public initReactI18next API.
  • feat(warnings): development-only warning (SUSPENDED_WHILE_LOADING, logged once) right before useTranslation suspends while translations are loading. With the default useSuspense: true and no <Suspense> boundary this previously surfaced as a blank screen or a cryptic React error; the warning now names both fixes (add a <Suspense> boundary or set react.useSuspense: false). No-op in production builds; the process.env.NODE_ENV check is wrapped so runtimes without a process global (raw ESM in the browser, some edge runtimes) stay silent instead of throwing.
  • ci: weekly workflow typechecking the test suite against @types/react@next / @types/react-dom@next, so the next React major's type changes (like the React 18 TFunctionResult/children wave) surface before user reports.

17.0.9

  • fix: allow TypeScript 7 in the optional typescript peer dependency range (^5 || ^6 || ^7). With typescript@7.0.2 in a project, npm install failed with an ERESOLVE peer conflict. Fixes #1927, thanks @​andikapradanaarif.
  • fix(types): <Trans t={t} ns="ns" …> with a t from useTranslation(['ns']) now typechecks under TypeScript 7. TS7 intersects the Ns inference candidates coming from the t prop (readonly ['ns']) and the ns prop ('ns') into an unsatisfiable 'ns' & readonly ['ns'], where TS6 resolved them. The ns prop on TransProps, TransSelectorProps and IcuTransWithoutContextProps now also accepts a single namespace out of an array-typed Ns (Ns | (Ns extends readonly (infer S extends string)[] ? S : never)) — which matches runtime behavior and is unchanged under TS5/TS6.
Commits
  • 274e2e6 17.0.11
  • 3c4c563 build
  • 1e7ccae chore: html-parse-stringify ^4.0.1 + 17.0.11 changelog
  • 4412e25 html-parse-stringify ^4.0.0: replace escapeLiteralLessThan with the parser's ...
  • 5787979 ci: types-compat falls back to latest when no @​types/react pre-release tag ex...
  • 3b71c27 17.0.10
  • 57c3500 build
  • c62476f chore: sync package-lock with i18next ^26.2.0 devDependency bump
  • 0126bd1 improve instance warnings (monorepo hint) + dev-only suspense warning + weekl...
  • 8b4a9ea 17.0.9
  • Additional commits viewable in compare view

Updates react-native from 0.79.7 to 0.85.2

Release notes

Sourced from react-native's releases.

0.85.2

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

Hermes dSYMS:

Hermes V1 dSYMS:

ReactNativeDependencies dSYMs:

ReactNative Core dSYMs:

... (truncated)

Changelog

Sourced from react-native's changelog.

Changelog (pre 0.80)

Commits
  • 67baaf3 Release 0.85.2
  • 5300582 Fix loading banner stuck after a reload
  • 430da64 Avoid moving RawProps during animation backend commit when retries are possib...
  • 16e6e32 Add pushAnimationMutations to the AnimationBackend (#56401)
  • 2c0ae27 Release 0.85.1
  • 9dfd26e fix: formData upload broken in debug builds (#56406)
  • 76cf797 Update generate-artifacts-executor scripts to skip write/cp for unchanged o...
  • 401b162 [0.85] Correclty promote flags to experimental for 0.85 release (#56373)
  • 10644a0 Release 0.85.0
  • b2839b1 Release 0.85.0-rc.7
  • Additional commits viewable 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

Updates react-native-screens from 4.24.0 to 4.26.2

Release notes

Sourced from react-native-screens's releases.

4.26.2

What's Changed

This patch release for 4.26.2 brings important stability improvements specifically for Android.

Key updates include preventing unexpected screen unmounting during fast navigation in Stack v5 by fixing transition finalization, as well as resolving a potential crash related to container state restoration in Tabs.

[!NOTE]

This version supports React Native 0.84+.

🐞 Bugfixes

  • fix(Android, Stack v5): Prevent screen unmounting on fast navigation (fix transition finalization) (#4342)
  • fix(Android, Tabs): fix potential crash with container state restoration (#4341)

Full Changelog: software-mansion/react-native-screens@4.26.1...4.26.2

4.26.1

What's Changed

This patch release for 4.26.1 brings a few targeted bug fixes for both iOS and Android, alongside a minor package configuration adjustment to improve dependency compatibility.

[!NOTE]

This version supports React Native 0.84+.

🐞 Bugfixes

  • fix(Android, Stack v4): default consume*Inset props to true (#4322)
  • fix(iOS, Split): Fix ShadowState inside SplitView columns after transition (#4309)

🔢 Misc

  • chore: remove explicit react-native peer dependency version from package config (#4328)
  • release: 4.26.1 (#4330)

Full Changelog: software-mansion/react-native-screens@4.26.0...4.26.1

4.26.0

What's Changed

This release brings a stable Tabs API along with numerous fixes, including improved coordination of FormSheet animations and keyboard interaction on Android, and fixed touch handling for Pressables in transparent headers on iOS.

We're also actively working on v5 of the library — this release adds an experimental standalone FormSheet component for both Android and iOS, and extends the menu API of the new Native Stack with several new features.

[!NOTE]

This version supports React Native 0.84+.

✅ Improvements

... (truncated)

Commits
  • 886754c release: 4.26.2
  • 7b280df fix(Android, Stack v5): Prevent screen unmounting on fast navigation (fix tra...
  • 970f950 fix(Android, Tabs): fix potential crash with container state restoration (#4341)
  • 7f2162b release: 4.26.1 (#4330)
  • 5767eff chore: remove explicit react-native peer dependency version from package conf...
  • f51e6eb fix(Android, Stack v4): default consume*Inset props to true (#4322)
  • fa041e7 fix(iOS, Split): Fix ShadowState inside SplitView columns after transition (#...
  • 7c1b491 release: 4.26.0 (#4304)
  • baeac78 fix(iOS): hide react symbols from swift (#4224)
  • 9d68e8f fix(iOS, Stack v4): fix header positioning in shadow tree (#4286)
  • 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

New Contributors

Full Changelog: software-mansion/react-native-svg@v15.15.4...v15.15.5

Commits
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for react-native-svg since your current version.


Updates @react-native-community/cli from 20.1.3 to 20.2.0

Commits

@dependabot
fix(deps)(deps): bump the dependencies group across 1 directory with …
bcb8742 
…18 updates

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

| Package | From | To |
| --- | --- | --- |
| [@shopify/flash-list](https://github.com/Shopify/flash-list) | `2.3.1` | `2.3.2` |
| [@walletconnect/react-native-compat](https://github.com/WalletConnect/walletconnect-monorepo/tree/HEAD/packages/react-native-compat) | `2.23.9` | `2.23.10` |
| [@walletconnect/utils](https://github.com/WalletConnect/walletconnect-monorepo/tree/HEAD/packages/utils) | `2.23.9` | `2.23.10` |
| [i18next](https://github.com/i18next/i18next) | `26.3.0` | `26.3.6` |
| [react](https://github.com/react/react/tree/HEAD/packages/react) | `19.2.5` | `19.2.8` |
| [@types/react](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react) | `19.2.16` | `19.2.18` |
| [react-i18next](https://github.com/i18next/react-i18next) | `17.0.8` | `17.0.11` |
| [react-native-safe-area-context](https://github.com/AppAndFlow/react-native-safe-area-context) | `5.7.0` | `5.8.0` |
| [react-native-screens](https://github.com/software-mansion/react-native-screens) | `4.24.0` | `4.26.2` |
| [react-native-svg](https://github.com/software-mansion/react-native-svg) | `15.15.4` | `15.15.5` |
| [@react-native-community/cli](https://github.com/react-native-community/cli/tree/HEAD/packages/cli) | `20.1.3` | `20.2.0` |
| [@react-native/jest-preset](https://github.com/react/react-native/tree/HEAD/packages/jest-preset) | `0.85.2` | `0.86.2` |
| [@types/react-dom](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react-dom) | `19.2.3` | `19.2.4` |
| [detox](https://github.com/wix/Detox) | `20.51.3` | `20.51.4` |
| [prettier](https://github.com/prettier/prettier) | `3.8.3` | `3.9.6` |
| [react-test-renderer](https://github.com/react/react/tree/HEAD/packages/react-test-renderer) | `19.2.7` | `19.2.8` |
| [ts-jest](https://github.com/kulshekhar/ts-jest) | `29.4.11` | `29.4.12` |



Updates `@shopify/flash-list` from 2.3.1 to 2.3.2
- [Release notes](https://github.com/Shopify/flash-list/releases)
- [Changelog](https://github.com/Shopify/flash-list/blob/main/CHANGELOG.md)
- [Commits](Shopify/flash-list@v2.3.1...v2.3.2)

Updates `@walletconnect/react-native-compat` from 2.23.9 to 2.23.10
- [Release notes](https://github.com/WalletConnect/walletconnect-monorepo/releases)
- [Changelog](https://github.com/WalletConnect/walletconnect-monorepo/blob/v2.0/packages/react-native-compat/CHANGELOG.md)
- [Commits](https://github.com/WalletConnect/walletconnect-monorepo/commits/@walletconnect/react-native-compat@2.23.10/packages/react-native-compat)

Updates `@walletconnect/utils` from 2.23.9 to 2.23.10
- [Release notes](https://github.com/WalletConnect/walletconnect-monorepo/releases)
- [Changelog](https://github.com/WalletConnect/walletconnect-monorepo/blob/v2.0/packages/utils/CHANGELOG.md)
- [Commits](https://github.com/WalletConnect/walletconnect-monorepo/commits/@walletconnect/utils@2.23.10/packages/utils)

Updates `i18next` from 26.3.0 to 26.3.6
- [Release notes](https://github.com/i18next/i18next/releases)
- [Changelog](https://github.com/i18next/i18next/blob/master/CHANGELOG.md)
- [Commits](i18next/i18next@v26.3.0...v26.3.6)

Updates `react` from 19.2.5 to 19.2.8
- [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.2.8/packages/react)

Updates `@types/react` from 19.2.16 to 19.2.18
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react)

Updates `react-i18next` from 17.0.8 to 17.0.11
- [Changelog](https://github.com/i18next/react-i18next/blob/master/CHANGELOG.md)
- [Commits](i18next/react-i18next@v17.0.8...v17.0.11)

Updates `react-native` from 0.79.7 to 0.85.2
- [Release notes](https://github.com/react/react-native/releases)
- [Changelog](https://github.com/react/react-native/blob/main/CHANGELOG-0.7x.md)
- [Commits](https://github.com/react/react-native/commits/v0.85.2/packages/react-native)

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

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

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

Updates `@react-native-community/cli` from 20.1.3 to 20.2.0
- [Release notes](https://github.com/react-native-community/cli/releases)
- [Changelog](https://github.com/react-native-community/cli/blob/main/packages/cli/CHANGELOG.md)
- [Commits](https://github.com/react-native-community/cli/commits/v20.2.0/packages/cli)

Updates `@react-native/jest-preset` from 0.85.2 to 0.86.2
- [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.86.2/packages/jest-preset)

Updates `@types/react` from 19.2.16 to 19.2.18
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react)

Updates `@types/react-dom` from 19.2.3 to 19.2.4
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react-dom)

Updates `detox` from 20.51.3 to 20.51.4
- [Release notes](https://github.com/wix/Detox/releases)
- [Commits](wix/Detox@20.51.3...20.51.4)

Updates `prettier` from 3.8.3 to 3.9.6
- [Release notes](https://github.com/prettier/prettier/releases)
- [Changelog](https://github.com/prettier/prettier/blob/main/CHANGELOG.md)
- [Commits](prettier/prettier@3.8.3...3.9.6)

Updates `react-test-renderer` from 19.2.7 to 19.2.8
- [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.2.8/packages/react-test-renderer)

Updates `ts-jest` from 29.4.11 to 29.4.12
- [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.11...v29.4.12)

---
updated-dependencies:
- dependency-name: "@shopify/flash-list"
  dependency-version: 2.3.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: "@walletconnect/react-native-compat"
  dependency-version: 2.23.10
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: "@walletconnect/utils"
  dependency-version: 2.23.10
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: i18next
  dependency-version: 26.3.6
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: react
  dependency-version: 19.2.8
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: "@types/react"
  dependency-version: 19.2.18
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: react-i18next
  dependency-version: 17.0.11
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: react-native
  dependency-version: 0.85.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: react-native-safe-area-context
  dependency-version: 5.8.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: react-native-screens
  dependency-version: 4.26.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: react-native-svg
  dependency-version: 15.15.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: "@react-native-community/cli"
  dependency-version: 20.2.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: "@react-native/jest-preset"
  dependency-version: 0.86.2
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: "@types/react"
  dependency-version: 19.2.18
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: "@types/react-dom"
  dependency-version: 19.2.4
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: detox
  dependency-version: 20.51.4
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: prettier
  dependency-version: 3.9.6
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: react-test-renderer
  dependency-version: 19.2.8
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: ts-jest
  dependency-version: 29.4.12
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file security Security related issue labels Aug 3, 2026
@dependabot
dependabot Bot deployed to security-review August 3, 2026 21:30 Active
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