Skip to content

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

Open
dependabot[bot] wants to merge 454 commits into
mainfrom
dependabot/npm_and_yarn/dependencies-bb6c0391ef
Open

fix(deps)(deps): bump the dependencies group across 1 directory with 24 updates#16
dependabot[bot] wants to merge 454 commits into
mainfrom
dependabot/npm_and_yarn/dependencies-bb6c0391ef

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 22, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

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

Package From To
@graphql-tools/schema 10.0.33 10.0.38
@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
bullmq 5.79.1 5.80.10
dompurify 3.4.11 3.4.12
i18next 26.0.8 26.3.6
react 19.2.5 19.2.8
@types/react 19.2.14 19.2.17
react-i18next 17.0.6 17.0.10
react-native 0.85.2 0.86.0
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.0
@semantic-release/release-notes-generator 14.1.0 14.1.1
detox 20.51.0 20.51.4
eslint-plugin-prettier 5.5.5 5.5.6
jest-circus 30.3.0 30.4.2
prettier 3.8.3 3.9.6
react-test-renderer 19.2.5 19.2.8
ts-jest 29.4.11 29.4.12
tsx 4.22.4 4.23.1

Updates @graphql-tools/schema from 10.0.33 to 10.0.38

Changelog

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

10.0.38

Patch Changes

  • Updated dependencies [e90719b]:
    • @​graphql-tools/utils@​11.2.2
    • @​graphql-tools/merge@​9.2.2

10.0.37

Patch Changes

  • Updated dependencies [615c1a2]:
    • @​graphql-tools/utils@​11.2.1
    • @​graphql-tools/merge@​9.2.1

10.0.36

Patch Changes

  • Updated dependencies [79f1998]:
    • @​graphql-tools/merge@​9.2.0

10.0.35

Patch Changes

  • Updated dependencies [2609c94]:
    • @​graphql-tools/utils@​11.2.0
    • @​graphql-tools/merge@​9.1.11

10.0.34

Patch Changes

  • Updated dependencies [981d461]:
    • @​graphql-tools/utils@​11.1.1
    • @​graphql-tools/merge@​9.1.10
Commits
  • 11f0a21 chore(release): update monorepo packages versions (#8303)
  • 3c27f9a chore(release): update monorepo packages versions (#8284)
  • 76b54da chore(release): update monorepo packages versions (#8264)
  • 062d229 chore(release): update monorepo packages versions (#8261)
  • c7f20ac chore(release): update monorepo packages versions (#8157)
  • See full diff in compare view

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 bullmq from 5.79.1 to 5.80.10

Release notes

Sourced from bullmq's releases.

v5.80.10

5.80.10 (2026-07-21)

Bug Fixes

v5.80.9

5.80.9 (2026-07-18)

Performance Improvements

  • flow-producer: reuse queue's shared Scripts instance in jobs fixes #4263 (#4308) (4f4b574)

v5.80.8

5.80.8 (2026-07-18)

Bug Fixes

  • scheduler: walk past stale slots when re-upserting under same id (#4299) (e8af563)

v5.80.7

5.80.7 (2026-07-17)

Bug Fixes

  • worker: move stalled job to failed when fetched manually (#4294) (c4a0a4a)

v5.80.6

5.80.6 (2026-07-17)

Bug Fixes

  • sandbox: preserve child_process exports in null-stdio (#4301) (5044cf8)

v5.80.5

5.80.5 (2026-07-16)

Bug Fixes

  • sandbox: kill children that fail init and surface refusal errors fixes #4283 (#4284) (7dd064e)

v5.80.4

5.80.4 (2026-07-15)

... (truncated)

Commits
  • 88730b0 fix(ci): remove stale OSV ignore (#4320)
  • 5e7f20f chore(deps): bump the npm_and_yarn group across 4 directories with 3 updates ...
  • 7603a78 chore(deps): update dependency brace-expansion to v5.0.7 [security] (#4318)
  • 71ec906 chore(deps): update devdependencies (non-major) [security] (#4314)
  • 097deaa ci: keep only one source of truth for dependencies [python] (#4310)
  • 788592b chore(release): 5.80.9 (#4309)
  • 4f4b574 perf(flow-producer): reuse queue's shared Scripts instance in jobs fixes #426...
  • 0715a56 chore(release): 5.80.8 (#4306)
  • e8af563 fix(scheduler): walk past stale slots when re-upserting under same id (#4299)
  • 096977e chore(release): 5.80.7 (#4304)
  • Additional commits viewable in compare view

Updates dompurify from 3.4.11 to 3.4.12

Release notes

Sourced from dompurify's releases.

DOMPurify 3.4.12

  • Fixed an issue where a hook would not get called for custom elements, thanks @​Rikuxx0
  • Hardened the handling of hooks removing elements, @​mkrause-bee360
  • Added support for a few new SVG attributes, thanks @​cbn-falias & @​Develop-KIM
  • Hardened the handling of declarative partial updates
  • Updated the documentation is several spots, README, wiki, etc.
  • Bumped several dependencies where possible
Commits

Updates i18next from 26.0.8 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).

v26.3.0

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

v26.2.0

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

v26.1.0

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

v26.0.10

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

v26.0.9

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

Sourced from i18next's changelog.

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

26.3.0

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

26.2.0

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

26.1.0

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

26.0.10

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

26.0.9

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

Commits

Updates react-i18next from 17.0.6 to 17.0.10

Changelog

Sourced from react-i18next's changelog.

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.

17.0.8

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

17.0.7

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

obaremoelijah274gmail.com and others added 30 commits April 24, 2026 12:02
Merge branch 'main' of https://github.com/obaremoelijah274-hash/SubTr…
e881f7f 
…ackr
@od-hunter
feat: implement subscription revenue recognition accounting
096aa00 
- Add contracts/src/revenue.rs with full revenue recognition module:
  - RevenueRecognitionRule (method + recognition_period)
  - Straight-line and usage-based recognition methods
  - RevenueSchedule / RevenueScheduleEntry types
  - Recognition snapshot and PeriodRevenue analytics types
  - generate_revenue_schedule, recognize_revenue, get_deferred_revenue,
    get_revenue_schedule, get_revenue_analytics_by_period
  - Deduplicating track_merchant_subscription
  - 21 Rust tests covering all paths, edge cases, and multi-element arrangements

- Update contracts/src/lib.rs:
  - Hook revenue schedule generation into charge_subscription
  - Add set_revenue_rule, recognize_revenue, get_deferred_revenue,
    get_revenue_schedule public contract APIs

- Add src/store/accountingStore.ts (Zustand + AsyncStorage):
  - setRecognitionRule / removeRecognitionRule
  - generateRevenueSchedule with straight-line and usage-based support
  - recognizeRevenue with pro-rated partial recognition
  - getDeferredRevenue per merchant
  - getRevenueAnalyticsByPeriod with configurable bucket size

- Add src/screens/RevenueReportScreen.tsx:
  - Recognised / deferred revenue summary cards
  - SVG bar chart by period (month / quarter / year)
  - Per-subscription recognition table
  - Revenue configuration panel (method toggle, simulate charge, reset)

- Add src/store/__tests__/accountingStore.test.ts:
  - 30 Jest tests covering pure helpers and all store actions
  - Edge cases: cancellation mid-period, rule updates, multi-element arrangements

- Wire RevenueReportScreen into bottom tab navigator (Revenue tab)
- Export useAccountingStore from store index
@od-hunter
chore: merge upstream/main and resolve conflicts
4fac118 
Conflicts resolved:
- contracts/src/lib.rs: kept our version (revenue module depends on it;
  upstream restructured contracts into a workspace but our standalone
  crate remains valid alongside the new structure)
- src/navigation/AppNavigator.tsx: merged upstream's new screens
  (Community, Profile, Segments, Gamification, Settings stack, GDPR,
  Language, Session, Admin, Error dashboards) with our RevenueReportScreen
- src/navigation/types.ts: merged upstream's new route types with our
  RevenueReport and RevenueTab additions
- src/store/index.ts: merged upstream's new store exports
  (useNetworkStore, useCommunityStore) with our useAccountingStore

Note: pre-existing lint errors in upstream files (unresolved module paths
for @shopify/flash-list, i18next, react-i18next) are not introduced by
this branch and exist on upstream/main.
@od-hunter
fix: integrate revenue module into workspace contract structure
791d707 
- Fix contracts/Cargo.toml: remove duplicate [package] section,
  make it a proper workspace root only
- Move revenue module from contracts/src/ to contracts/subscription/src/
  adapted for the new storage-contract delegation pattern
- Add revenue StorageKey variants to contracts/types/src/lib.rs:
  RevenueRecognitionRule, RevenueSchedule, RevenueDeferredBalance,
  RevenueRecognisedBalance, RevenueMerchantSubscriptions
- Hook revenue schedule generation into charge_subscription in
  contracts/subscription/src/lib.rs
- Add revenue public API to SubTrackrSubscription:
  set_revenue_rule, recognize_revenue, get_deferred_revenue,
  get_revenue_schedule
- Fix clippy::manual_div_ceil in revenue.rs (use .div_ceil())
- Add #[allow(clippy::too_many_arguments)] to subscription and proxy
  crates (pre-existing upstream issue with Soroban contractimpl macro)
- Remove obsolete contracts/src/ directory
- All workspace tests pass, cargo fmt --check clean, clippy -D warnings clean
@Smartdevs17
Merge pull request #308 from od-hunter/feat/revenue-recognition-accou…
de0682d 
…nting

feat: implement subscription revenue recognition accounting
@Smartdevs17
Merge pull request #304 from shaaibu7/feature/subscription-invoicing
f99eb2a 
Feature/subscription invoicing
@Smartdevs17
Merge main into 291
5b65bde
@Smartdevs17
Merge pull request #310 from Smartdevs17/ci-optimizations-fixed
3e3fd86 
CI/CD pipeline optimizations
@Smartdevs17
Merge main into 284
0c250ba
@Smartdevs17
Merge pull request #311 from Smartdevs17/feat-pricing-fixed
049c83d 
Feat: implement subscription price optimization engine
@Smartdevs17
Merge main
451b5b5
@Smartdevs17
Merge pull request #314 from Smartdevs17/feat-webhooks-fixed
4ce62e9 
Feat: implement subscription webhooks
@Smartdevs17
Merge
1ba4ab0
@Smartdevs17
Merge pull request #315 from Smartdevs17/feat-gating-fixed
e17a4c6 
Feature: subscription feature gating
@Smartdevs17
Merge
2ee5883
@Smartdevs17
Merge pull request #316 from Smartdevs17/feat-batching-new
d0f773a 
Implement subscription transaction batching and aggregation
@Smartdevs17
Merge
12980ce
@Smartdevs17
Merge pull request #317 from Smartdevs17/feat-logging-fixed
0f5b0e6 
feat: implemented logging system
@Smartdevs17
Merge
3104417
@Smartdevs17
Merge pull request #318 from Smartdevs17/feat-animations-fixed
bdcda1b 
Feature: animated transitions
@Smartdevs17
Merge
345b060
@Smartdevs17
Merge pull request #319 from Smartdevs17/feat-logging2-fixed
f2833da 
feat: implemented logging system
@Smartdevs17
Merge
d7112bb
@Smartdevs17
Merge pull request #320 from Smartdevs17/feat-invariant-fixed
2fe107d 
Feat(contracts): implement subscription contract invariant testing suite
@Smartdevs17
Merge
9dfcb86
@Smartdevs17
Merge pull request #321 from Smartdevs17/feat-sla-old-fixed
bd51d6a 
Feat/sla monitoring reporting
@Smartdevs17
Merge
e32ba3f
@Smartdevs17
Merge pull request #322 from Smartdevs17/feat-wallet-v2-fixed
2affffa 
Feat: improve WalletConnect v2 support
@Smartdevs17
Merge
e4523ab
@Smartdevs17
Merge pull request #323 from Smartdevs17/feat-gesture-fixed
491fa9f 
Feat: improve subscription gesture handling
Ebuka321 and others added 27 commits June 29, 2026 13:38
@Ebuka321
Merge pull request #659 from Eromosele0110/issue-557-tax-engine
fa997d9 
feat: implement tax compliance engine with Avalara/TaxJar integration…
@Eromosele0110
Merge branch 'main' into issue-555-credit-prepayment
b0836cc
@Ebuka321
Merge pull request #657 from Eromosele0110/issue-555-credit-prepayment
d4e0b91 
feat: implement credit note and prepayment wallet management (#555)
@topboy192
Merge branch 'main' into feat/559-customer-health-scoring
8a4e623
@Ebuka321
Merge pull request #682 from topboy192/feat/559-customer-health-scoring
1d38ef3 
Feat/559 customer health scoring
@my908-hue
A configurable PII classification engine with regex/ML-based pattern …
35149b0 
…detection, where it flows, and how it is protected. (#702)
@uboho-prog
Add webhook HMAC signature verification, nonce replay protection, and…
a8faaf2 
… key rotation support (#701)
@Tekprecious @whitezaddy
Feature/rbac implementation (#700)
bd18214 
* feat(auth): implement rbac schema, guards, and role management screen

* fix(auth): resolve line-ending formats and code style gate requirements

---------

Co-authored-by: whitezaddy <austinihueze@gmail.com>
@Yash-Karakoti
feat: add full stack local development environment with docker compos…
0b9a78a 
…e (#616) (#699)
@yusufadeagbo
perf: add composite query indexes and slow-query monitor (#698)
bbf5a81
@wagmiiii
feat: implement MEV protection and commit-reveal for subscription cha…
4d37237 
…rges (#640)
@sheyman546
feat: add network detection and switching (#69) (#641)
922ce09 
* fix(ci): resolve TS ESLint Prettier audit failures for PR 641

* fix(ci): resolve Rust Clippy and TypeScript Build failures

* fix(test): add ThemeProvider to shared test wrapper

* fix(clippy): remove duplicate #![cfg(test)] from api and credit test files

* fix(clippy): remove duplicate #![cfg(test)] from access_control test file
@abimbolaalabi
feat(navigation): refactor to type-safe React Navigation with deep li…
7516bea 
…… (#474)

* feat: squashed routes branch with secrets removed

Co-authored-by: od-hunter <146340502+od-hunter@users.noreply.github.com>
Co-authored-by: abimbolaalabi <ibrahimade92@gmail.com>

Includes all changes from the routes branch history:
- Redis distributed cache for plan metadata
- All previous features, fixes, and optimizations
- Hardcoded secrets replaced with environment variables

* fix: use env var fallback in redis test to avoid hardcoded password
@rindicomfort
feat: Add gradient-based gas optimization profiling to Soroban contra…
7d5d82e 
…ct CI pipeline (#696)

* feat: add gas-based profiling and regression checks to Soroban CI pipeline

* chore: target subtrackr-proxy package in gas-benchmark script
@jadonamite
feat(db): Database connection multiplexing for serverless environment…
57d61c5 
…s (#600) (#651)

* feat(db): connection multiplexing for serverless environments (#600)

Route serverless DB access through a transaction-pooling proxy (RDS Proxy
or PgBouncer) so a small set of backend connections is multiplexed across
many concurrent function invocations, preventing connection exhaustion.

- backend/shared/db/serverlessPool.ts: transaction-pooling adapter with
  IAM/SCRAM-256 auth, credential refresh, withClient/withTransaction
  helpers, and abandoned-connection leak detection (>30s force-close).
- backend/serverless/dbConfig.ts + withDatabase.ts: env-driven pool config
  (RDS IAM token provider) and a Lambda wrapper that releases the client in
  a finally block after every invocation.
- backend/monitoring/connectionPoolMetrics.ts: Prometheus pool/leak metrics
  and structured leak alerting.
- infra/terraform/{rds_proxy,pgbouncer}.tf: proxy provisioning (max ~50
  pooled connections serving 500+ functions, transaction pooling).
- docker-compose.yml + .env.example: local PgBouncer + Postgres for parity;
  all credentials read from a gitignored .env (no hardcoded secrets).

Closes #600

* fix(deps): repair malformed package.json blocking install

The dependencies block had a duplicate "zustand" entry and missing
commas, producing invalid JSON that breaks `npm install` in CI. Keep a
single zustand ^5.0.0 and the redis ^4.6.7 entry.
@jadonamite
feat(notification): XSS protection for rich-text template fields (#61…
dece4bc 
…1) (#652)

Sanitize rich-text email/notification templates server-side so stored HTML
can never carry executable markup, with CSP defence-in-depth on the admin
dashboard.

- backend/shared/sanitizer: HTMLSanitizerService wrapping DOMPurify (via
  jsdom) with a strict tag/attribute allowlist, http/https/mailto-only href
  protocols, full SVG/script/iframe stripping, and forced rel=noreferrer on
  links.
- backend/shared/middleware/cspMiddleware.ts: hardened CSP
  (script-src 'self', object-src 'none') plus companion security headers,
  with Express and Next.js adapters.
- backend/services/notification/templateService.ts: sanitize body on save,
  strip HTML from subjects, and render a sanitized preview before save.
- backend/services/notification/jobs/backScanTemplates.ts: idempotent cron
  that quarantines and re-sanitizes pre-existing unsafe templates.
- developer-portal/utils/securityHeaders.ts: applies the shared CSP to admin
  dashboard routes.
- package.json: add dompurify, jsdom, @types/jsdom.

Closes #611
@benedictworks-home
refactor: implement unified CoreError enum and migrate 14 contracts (…
e3aa8d6 
…#638)
@AlphaTechini
feat: add response compression and stream negotiation for API gateway…
01c54f1 
… (#627)
@sheyman546
fix(#62,#69): consolidate walletStore with walletServiceManager and a…
7ffaea4 
…dd network detection UI (#499)

- walletStore now derives all connection state (address, chainId, network,
  isConnected) from walletServiceManager via a listener subscription, making
  walletServiceManager the single source of truth (#62)
- Added setPreferredNetwork, detectNetworkMismatch, and networkMismatch state
  to walletStore for EVM network mismatch detection (#69)
- WalletConnectScreen: added network mismatch warning banner and a bottom-sheet
  network picker modal (FlatList of ALL_NETWORKS) so users can switch their
  preferred network without leaving the screen (#69)
- Updated integration.test.ts walletStore suite to match the new consolidated
  API: removed stale wallet/\@subtrackr_wallet references, added mock for
  walletService and networkService, added tests for syncWalletConnection,
  listener-driven sync, and network mismatch detection

Closes #62
Closes #69
@Smartdevs17
fix: resolve lint, typecheck, and all 736 tests (70/70 suites)
0140ba1 
- Fix 43 failing test suites: fixed assertions, mocks, snapshot calls,
  ThemeProvider wrapping, and integration test timer/environment issues
- Fix TypeScript strict errors across 50+ files (stores, services, screens,
  navigation, themes, types, hooks, jest config)
- Fix ESLint errors (0 errors, 103 warnings remaining)
- Add .eslintignore for services/ and node_modules/
- Add @babel/plugin-transform-flow-strip-types for RN Flow type parsing
- Deduplicate package.json (express, @types/express)
- Rename src/utils/__tests__/accessibility.test.ts → accessibility.ts to
  avoid being picked up as test file
- Add proper TypeScript types to all zustand stores with persist middleware
- Fix navigation types and AppNavigator stray JSX
@Smartdevs17
fix: replace snapshot tests with render assertions for CI compatibility
05c0843 
Snapshots are not tracked in git (gitignored *.snap) and differ
between macOS and Linux CI runners. Replace toMatchSnapshot()
with getByRole/getByText expectations.
@Smartdevs17
fix: update CI workflows - bump actions versions, fix format command,…
a4053a5 
… remove broken jobs
@Smartdevs17
ci: strip to minimal jobs (lint, typecheck, test, audit)
aa42928
@Smartdevs17
ci: exclude test files from typecheck, fix prettier formatting
068876a
@Smartdevs17
chore: remove dead directories and clean up config refs
ea98a62
@Smartdevs17
ci: disable all broken workflows except minimal CI
550b1b8
@dependabot
fix(deps)(deps): bump the dependencies group across 1 directory with …
db2761d 
…24 updates

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

| Package | From | To |
| --- | --- | --- |
| [@graphql-tools/schema](https://github.com/ardatan/graphql-tools/tree/HEAD/packages/schema) | `10.0.33` | `10.0.38` |
| [@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` |
| [bullmq](https://github.com/taskforcesh/bullmq) | `5.79.1` | `5.80.10` |
| [dompurify](https://github.com/cure53/DOMPurify) | `3.4.11` | `3.4.12` |
| [i18next](https://github.com/i18next/i18next) | `26.0.8` | `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.14` | `19.2.17` |
| [react-i18next](https://github.com/i18next/react-i18next) | `17.0.6` | `17.0.10` |
| [react-native](https://github.com/facebook/react-native/tree/HEAD/packages/react-native) | `0.85.2` | `0.86.0` |
| [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/facebook/react-native/tree/HEAD/packages/jest-preset) | `0.85.2` | `0.86.0` |
| [@semantic-release/release-notes-generator](https://github.com/semantic-release/release-notes-generator) | `14.1.0` | `14.1.1` |
| [detox](https://github.com/wix/Detox) | `20.51.0` | `20.51.4` |
| [eslint-plugin-prettier](https://github.com/prettier/eslint-plugin-prettier) | `5.5.5` | `5.5.6` |
| [jest-circus](https://github.com/jestjs/jest/tree/HEAD/packages/jest-circus) | `30.3.0` | `30.4.2` |
| [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.5` | `19.2.8` |
| [ts-jest](https://github.com/kulshekhar/ts-jest) | `29.4.11` | `29.4.12` |
| [tsx](https://github.com/privatenumber/tsx) | `4.22.4` | `4.23.1` |



Updates `@graphql-tools/schema` from 10.0.33 to 10.0.38
- [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.0.38/packages/schema)

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 `bullmq` from 5.79.1 to 5.80.10
- [Release notes](https://github.com/taskforcesh/bullmq/releases)
- [Commits](taskforcesh/bullmq@v5.79.1...v5.80.10)

Updates `dompurify` from 3.4.11 to 3.4.12
- [Release notes](https://github.com/cure53/DOMPurify/releases)
- [Commits](cure53/DOMPurify@3.4.11...3.4.12)

Updates `i18next` from 26.0.8 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.0.8...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.14 to 19.2.17
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react)

Updates `react-i18next` from 17.0.6 to 17.0.10
- [Changelog](https://github.com/i18next/react-i18next/blob/master/CHANGELOG.md)
- [Commits](i18next/react-i18next@v17.0.6...v17.0.10)

Updates `react-native` from 0.85.2 to 0.86.0
- [Release notes](https://github.com/facebook/react-native/releases)
- [Changelog](https://github.com/react/react-native/blob/main/CHANGELOG.md)
- [Commits](https://github.com/facebook/react-native/commits/v0.86.0/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.0
- [Release notes](https://github.com/facebook/react-native/releases)
- [Changelog](https://github.com/react/react-native/blob/main/CHANGELOG.md)
- [Commits](https://github.com/facebook/react-native/commits/v0.86.0/packages/jest-preset)

Updates `@semantic-release/release-notes-generator` from 14.1.0 to 14.1.1
- [Release notes](https://github.com/semantic-release/release-notes-generator/releases)
- [Commits](semantic-release/release-notes-generator@v14.1.0...v14.1.1)

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

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

Updates `eslint-plugin-prettier` from 5.5.5 to 5.5.6
- [Release notes](https://github.com/prettier/eslint-plugin-prettier/releases)
- [Changelog](https://github.com/prettier/eslint-plugin-prettier/blob/main/CHANGELOG.md)
- [Commits](prettier/eslint-plugin-prettier@v5.5.5...v5.5.6)

Updates `jest-circus` from 30.3.0 to 30.4.2
- [Release notes](https://github.com/jestjs/jest/releases)
- [Changelog](https://github.com/jestjs/jest/blob/main/CHANGELOG.md)
- [Commits](https://github.com/jestjs/jest/commits/v30.4.2/packages/jest-circus)

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

Updates `tsx` from 4.22.4 to 4.23.1
- [Release notes](https://github.com/privatenumber/tsx/releases)
- [Changelog](https://github.com/privatenumber/tsx/blob/master/release.config.cjs)
- [Commits](privatenumber/tsx@v4.22.4...v4.23.1)

---
updated-dependencies:
- dependency-name: "@graphql-tools/schema"
  dependency-version: 10.0.38
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: 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: bullmq
  dependency-version: 5.80.10
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: dompurify
  dependency-version: 3.4.12
  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-minor
  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.17
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: react-i18next
  dependency-version: 17.0.10
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: react-native
  dependency-version: 0.86.0
  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.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: "@semantic-release/release-notes-generator"
  dependency-version: 14.1.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: "@types/react"
  dependency-version: 19.2.17
  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: eslint-plugin-prettier
  dependency-version: 5.5.6
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: jest-circus
  dependency-version: 30.4.2
  dependency-type: direct:development
  update-type: version-update:semver-minor
  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
- dependency-name: tsx
  dependency-version: 4.23.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Jul 22, 2026
@dependabot @github

dependabot Bot commented on behalf of github Jul 22, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: security. 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

dependencies Pull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.