Bumping react-native to 0.85.3 while react-native-macos stays at 0.73.34 and @react-native/babel-preset, @react-native/metro-config, and @react-native/typescript-config stay at 0.73.x creates a 12-minor-version mismatch that will likely cause build failures and runtime errors in the macOS sample — react-native-macos must be kept in sync with the react-native version it forks.

The updater script scripts/update-rn.sh runs yarn up react-native@<version> across the monorepo, which propagated 0.85.3 into samples/react-native-macos/package.json. That sample, however, also depends on react-native-macos@0.73.34 (a fork that mirrors a specific RN minor version) and pins react@18.2.0 and @react-native/babel-preset|metro-config|typescript-config@0.73.x. RN 0.85 requires React 19 and matching @react-native/* toolchain (see samples/react-native/package.json which was updated to React 19.2.3 / @react-native/* 0.85.1 in the same PR). Mixing react-native@0.85.3 with react-native-macos@0.73.34 will break native module registration and Metro bundling for the macOS sample. Since react-native-macos has no 0.85 release, the correct fix is to pin/exclude this workspace from the yarn up so the sample continues to match its macOS fork version.