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

[dependabot]

Bumps the dependencies group with 18 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.4.0
react	19.2.5	19.2.8
@types/react	19.2.16	19.2.18
react-i18next	17.0.8	17.0.12
react-native	0.85.2	0.87.0
react-native-safe-area-context	5.7.0	5.9.1
react-native-screens	4.24.0	4.27.0
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.87.0
@types/react-dom	19.2.3	19.2.5
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

• fix(recycling): disable removeClippedSubviews to prevent Android crash by @​shopify-github-actions-access[bot] in Shopify/flash-list#2202
• fix: scroll to index autoscroll race by @​isekovanic in Shopify/flash-list#2290
• feat(sticky-headers): configure sticky header zIndex by @​GurkarnSD in Shopify/flash-list#2311

New Contributors

• @​isekovanic made their first contribution in Shopify/flash-list#2290
• @​GurkarnSD made their first contribution in Shopify/flash-list#2311

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

• #7250 fcaaf3f Thanks @​github-actions! - chore: update yttrium native dependencies
  • Update yttrium-wcpay (Android) to 0.10.58

Changelog

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

2.23.10

Patch Changes

• #7250 fcaaf3f Thanks @​github-actions! - chore: update yttrium native dependencies
  • Update yttrium-wcpay (Android) to 0.10.58

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

Release notes

Sourced from i18next's releases.

v26.4.0

• perf: cache toResolveHierarchy results per (code, fallbackCode) pair. The hierarchy resolver runs on every t() call and calls Intl.getCanonicalLocales multiple times, which showed up prominently when profiling render-heavy UIs (e.g. virtualized data grids); with the cache the per-call cost drops from ~886 ns to ~41 ns. The cache is invalidated automatically when options.fallbackLng changes (reassignment or in-place array mutation); if you mutate other resolution-relevant options at runtime (load, lowerCaseLng, cleanCode, nonExplicitSupportedLngs), call i18next.services.languageUtils.clearCache() afterwards. Function-valued fallbackLng and per-call array/object fallbackLng options are never cached, so dynamic fallbacks keep working as before. Thanks @​equaterina (#2444).
• chore: update all devDependencies (Babel stays on 7.x until @rollup/plugin-babel supports 8, eslint on 9.x for neostandard). Removed the unused coveralls package (CI uses the Coveralls GitHub Action) and replaced sinon with nise + vitest.spyOn in the v1 compatibility tests, which resolves all open npm audit findings (0 vulnerabilities) and should close the dependabot alerts on the lockfile.

v26.3.6

• fix: allow TypeScript 7 in the optional typescript peer dependency range (^5 || ^6 || ^7). With [email protected] 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.4.0

• perf: cache toResolveHierarchy results per (code, fallbackCode) pair. The hierarchy resolver runs on every t() call and calls Intl.getCanonicalLocales multiple times, which showed up prominently when profiling render-heavy UIs (e.g. virtualized data grids); with the cache the per-call cost drops from ~886 ns to ~41 ns. The cache is invalidated automatically when options.fallbackLng changes (reassignment or in-place array mutation); if you mutate other resolution-relevant options at runtime (load, lowerCaseLng, cleanCode, nonExplicitSupportedLngs), call i18next.services.languageUtils.clearCache() afterwards. Function-valued fallbackLng and per-call array/object fallbackLng options are never cached, so dynamic fallbacks keep working as before. Thanks @​equaterina (#2444).
• chore: update all devDependencies (Babel stays on 7.x until @rollup/plugin-babel supports 8, eslint on 9.x for neostandard). Removed the unused coveralls package (CI uses the Coveralls GitHub Action) and replaced sinon with nise + vitest.spyOn in the v1 compatibility tests, which resolves all open npm audit findings (0 vulnerabilities) and should close the dependabot alerts on the lockfile.

26.3.6

• fix: allow TypeScript 7 in the optional typescript peer dependency range (^5 || ^6 || ^7). With [email protected] 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

• 652847e 26.4.0
• 6c6025f prettier fix
• 742b9a9 chore: update dependencies and clean up dev tooling
• 06924d9 fix: invalidate toResolveHierarchy cache on in-place fallbackLng mutation
• bb80369 perf: cache toResolveHierarchy (#2444)
• 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...
• 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

• Performance improvements when decoding (#37087 by @​eps1lon)

19.2.7 (June 1st, 2026)

React Server Components

• Fixed missing FormData entries in Server Actions which regressed in 19.2.6 (#36566 by @​unstubbable)

19.2.6 (May 6th, 2026)

React Server Components

• Type hardening and performance improvements (#36425 by @​eps1lon and @​unstubbable)

Changelog

Sourced from react's changelog.

19.2.7 (June 1, 2026)

React Server Components

• Fixed missing FormData entries in Server Actions which regressed in 19.2.6 (@​unstubbable #36566)

19.2.6 (May 6, 2026)

React Server Components

• Type hardening and performance improvements (@​eps1lon, @​unstubbable #36425)

Commits

• 1dd4ecb [FlightReply] Performance improvements when decoding (#37087)
• b0d2fdb [19.2.x] Update required references to GitHub repo (#36753)
• 6117d7c Version 19.2.7 (#36591)
• eaf3e95 Version 19.2.6
• See full diff in compare view

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

• See full diff in compare view

Updates react-i18next from 17.0.8 to 17.0.12

Changelog

Sourced from react-i18next's changelog.

17.0.12

• fix(IcuTrans): key-less icu.macro nodes (<Trans>Welcome, {name}!</Trans>, <Select>, <Plural> without i18nKey) rendered an empty string since 17.0.0. The macro now emits <IcuTrans defaultTranslation="…"> without a key and IcuTrans passed undefined to t(), which returns ''. Like Trans, IcuTrans now uses defaultTranslation as the key when i18nKey is not provided.

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 [email protected] 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

• ea721fb 17.0.12
• 6c2a71e fix(IcuTrans): use defaultTranslation as key when no i18nKey is given
• 258c96d chore(examples): upgrade all example apps off unmaintained toolchains
• b8677c8 chore: update dependencies to close dependabot alerts
• aa9c92b docs: point Trans component links at the current docs (#1929)
• 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...
• Additional commits viewable in compare view

Updates react-native from 0.85.2 to 0.87.0

Release notes

Sourced from react-native's releases.

0.87.0

---

Hermes V1 dSYMS:

• Debug
• Release

ReactNativeDependencies dSYMs:

• Debug
• Release

ReactNative Core dSYMs:

• Debug
• Release

---

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.87.0-rc.4

---

Hermes V1 dSYMS:

• Debug
• Release

ReactNativeDependencies dSYMs:

• Debug
• Release

ReactNative Core dSYMs:

• Debug
• Release

---

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

---

... (truncated)

Changelog

Sourced from react-native's changelog.

v0.87.0

Breaking

• Appearance: Fix return type of useColorScheme() hook (now ColorSchemeName | null) (ef6463c25d by @​huntie)
• Appearance: useColorScheme() no longer returns 'unspecified' (this was always the case, but is a breaking type change) (8ac88f481a by @​huntie)
• CLI: The react-native/core-cli-utils package is no longer published. It remains available in the React Native repo as a reference implementation. (9c3fddf9cd by @​huntie)
• Hermes: Remove Legacy Hermes from C++ code (f9476256bd by @​cipolleschi)
• JavaScript API: Deep imports to 'react-native/src/private/...' have been restricted, and are no longer visible to TypeScript. These subpaths still exist, but do not have type coverage. (142b6172a9 by @​huntie)
• JavaScript API: The NativeDialogManagerAndroid export is removed. (a793d21a7e by @​huntie)
• JavaScript API: The Touchable root export (undocumented) is removed. If you are extending Touchable as a type, please use ViewProps instead. (6fbf3062f9 by @​huntie)
• JavaScript API: react-native/rn-get-polyfills is removed — please use react-native/js-polyfills (package) (b6a535afee by @​huntie)
• Jest: react-native/jest-preset is removed — all projects must now migrate to react-native/jest-preset (package) (9ee21ddd9b by @​huntie)
• Legacy Architecture: Compile out RuntimeScheduler_Legacy under RCT_REMOVE_LEGACY_ARCH (d205267a5f by @​christophpurrer)
• LogBox: Set max font scaling in LogBox to avoid layout breaking (4aef2b0126 by @​pchalupa)
• Node: Require Node.js >= 22.13.0 (a0d39e7a9c by @​huntie)
• React Native DevTools: Remove support for connecting to the standalone react-devtools package via WebSocket. Use React Native DevTools instead. (f1971caa44 by @​huntie)
• Renderer: Remove RawPropsKey prefix and suffix (67381e157f by @​javache)
• Runtime: Remove the SceneTracker module from Libraries/Utilities, stop setting the active scene from AppRegistry.runApplication, and pass the app key as an optional second argument to WrapperComponentProvider (bbb5be9b41 by @​rubennorte)
• ScrollView: Remove deprecated boolean values support for ScrollView keyboardShouldPersistTaps (5bf3e38db2 by @​zoontek)
• StatusBar: Remove deprecated StatusBar backgroundColor / translucent / networkActivityIndicatorVisible props and setBackgroundColor / setTranslucent / setNetworkActivityIndicatorVisible methods (6b45e579d6 by @​zoontek)
• Strict TypeScript API: Remove legacy NativeMethods and NativeMethodsMixin types (b724611aec by @​huntie)
• Strict TypeScript API: React Native's default JavaScript API is now the Strict TypeScript API. Use customConditions: ["react-native-legacy-deep-imports"] to opt out. (c948b61c05 by @​huntie)

Android specific

• AGP: Adopt AGP v9 (abb071b135 by @​hurali97)

iOS specific

• Build: [0.87] Pick SwiftPM support chain (#57442, #57332, #57564) (486df8d410 by @​cipolleschi)
• Build: Ship a version-stamped ReactNativeVersion.h in the prebuilt iOS core artifacts instead of the 1000.0.0 dev sentinel (95df50034b by @​chrfalch)
• Legacy Architecture: Remove depracted legacy architecture protocol APIs (ad9936faf6 by @​christophpurrer)
• Legacy Architecture: Remove unused legacy architecture RCTAppSetupUtils methods (40b16dca9f by @​christophpurrer)
• Legacy Architecture: Remove RCTBridge Functions from RCTReactNativeFactory Header (75eaff4c03 by @​christophpurrer)
• Legacy Architecture: Remove unused bridge-based RCTTurboModuleManager initializer (cb74b82309 by @​christophpurrer)
• Legacy Architecture: RNTester / RCTReactNativeFactory remove unused new architecture flags and RCTArchConfiguratorProtocol (2148f15db5 by @​christophpurrer)
• Legacy Architecture: Remove 6 empty Objective-C stub headers (23ce90bd3b by @​christophpurrer)
• Legacy Architecture: Remove legacy architecture code guarded by RCT_REMOVE_LEGACY_ARCH from RN iOS (86350ab988 by @​christophpurrer)
• Legacy Architecture: Removing further legacy arch symbols such as RCTCxxBridge (c65281581d by @​javache)

Added

• Animated: Support native driven AnimatedValue interpolation easing (57ce6bc585 by @​zeyap)
• Animated: Remove useNativeDriver under featureflag animatedForceNativeDriver (9cf30b6e4b by @​zeyap)
• Animated: Remove useNativeDriver under featureflag animatedForceNativeDriver (cffe14ff57 by @​zeyap)
• Animated: Add optimizedAnimatedPropUpdates feature flag (ed96b22af2 by Bartlomiej Bloniarz)
• Assets: Introduce react-native/asset-utils package (relocates Android path utils for libraries/frameworks) (41d52189e2 by @​huntie)
• JavaScript API: Deprecate 'react-native/Libraries/Core/InitializeCore'. Use 'react-native/setup-env' instead. (bfa679f0ea by @​huntie)
• Legacy Architecture: Gate shared C++ and Android Java/Kotlin legacy view manager interop behind RCT_REMOVE_LEGACY_COMPONENT_INTEROP (9885fe95ef by @​christophpurrer)

... (truncated)

Commits

• 4bc2473 Release 0.87.0
• 01f752d Release 0.87.0-rc.4
• 24353da fix(iOS): keep prebuilt Headers/ in place on a Debug/Release swap (#57814)
• 329f864 fix(swiftpm): persist --config-command so the in-build sync keeps using it (#...
• 4dd4d31 Write the prebuilt module-map flag to OTHER_CPLUSPLUSFLAGS too (#57742)
• f3e11c2 Fix compat with extensionless scripts/* imports (#57718)
• d8b52df SPM: allow overriding the autolinking config command (#57662)
• 0cacb90 SPM: fix raw Flow type annotations in bare-node scripts (#57660)
• 034245a fix(iOS): stage Hermes headers in prebuild compose job so ReactNativeHeaders ...
• b67c5cf Release 0.87.0-rc.3
• Additional commits viewable in compare view

Maintainer changes

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

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

Release notes

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

Release 5.9.1

5.9.1 (2026-08-18)

Bug Fixes

• register src/paper/java as a Java source set on old architecture (#755) (780f599), closes