react-native@0.85.3 peerDependencies allow react@19.2.6 but embedded renderer requires exact 19.2.3

[ArcSolver]

Description

react-native@0.85.3 declares this peer dependency:

{
  "react": "^19.2.3"
}

That allows package managers to install react@19.2.6, but the embedded React Native renderer in the same package appears to require react@19.2.3 exactly at runtime.

In Libraries/Renderer/implementations/ReactNativeRenderer-dev.js from react-native@0.85.3:

var isomorphicReactPackageVersion = React.version;
if ("19.2.3" !== isomorphicReactPackageVersion)
  throw Error(
    'Incompatible React versions: The "react" and "react-native-renderer" packages must have the exact same version. Instead got:\n  - react:                  ' +
      (isomorphicReactPackageVersion +
        "\n  - react-native-renderer:  19.2.3\nLearn more: https://react.dev/warnings/version-mismatch")
  );

The renderer internals also report:

version: "19.2.3",
rendererPackageName: "react-native-renderer",
reconcilerVersion: "19.2.3"

So the install-time contract says react@19.2.6 is acceptable, while the runtime contract rejects it.

Steps to reproduce

1. Install react-native@0.85.3.
2. Install react@19.2.6 and react-dom@19.2.6.
3. Launch a React Native app.

Expected behavior

The package metadata should prevent installing a React version that the embedded renderer will reject at runtime, or tooling/docs should make this exact-version requirement explicit enough to catch before app launch.

For example, one of these would avoid the mismatch:

• narrow react-native@0.85.3's peerDependencies.react to the exact renderer-compatible version, 19.2.3, or
• add install/doctor guidance that react must exactly match the embedded react-native-renderer version, not just satisfy the semver peer range.

Actual behavior

react@19.2.6 satisfies ^19.2.3, but the app fails at runtime because the embedded react-native-renderer is 19.2.3.

Environment

Observed from package contents:

{
  "reactNativeVersion": "0.85.3",
  "reactPeer": "^19.2.3",
  "rendererCheck": "19.2.3",
  "rendererVersion": "19.2.3"
}

This came up in a pnpm monorepo where web packages resolve react@19.2.6 and an Expo/RN mobile app correctly needs react@19.2.3. The monorepo context made the mismatch more visible, but the underlying issue seems to be that the package metadata permits a React patch version that the renderer rejects.

[react-native-bot]

Warning

Missing reproducer: We could not detect a reproducible example in your issue report. Reproducers are mandatory and we can accept only one of those as a valid reproducer:

• For majority of bugs: send us a Pull Request with the RNTesterPlayground.js edited to reproduce your bug.
• If your bug is UI related: a Snack
• If your bug is build/upgrade related: a project using our Reproducer Template

You can read more about about it on our website: How to report a bug.

[ArcSolver]

Added a public reproducer using the React Native Reproducer Template:

https://github.com/ArcSolver/rn-0853-react-1926-renderer-repro

The reproducer intentionally uses:

{
  "react": "19.2.6",
  "react-native": "0.85.3"
}

This satisfies react-native@0.85.3's published peerDependencies.react = ^19.2.3, but the installed renderer still checks for exact 19.2.3 at runtime.

Local package inspection from the reproducer after install:

{
  "reactVersion": "19.2.6",
  "reactNativeVersion": "0.85.3",
  "reactNativePeerReact": "^19.2.3",
  "rendererCheck": "19.2.3",
  "rendererVersion": "19.2.3"
}

Expected launch failure:

Incompatible React versions: The "react" and "react-native-renderer" packages must have the exact same version.
Instead got:
  - react:                  19.2.6
  - react-native-renderer:  19.2.3