chore(0.85): prepare stable 0.85.0 with React Native 0.85.3 by Saadnajmi · Pull Request #3034 · microsoft/react-native-macos

Saad Najmi (Saadnajmi) · 2026-07-17T13:01:59Z

Current release stack

Tracker: React Native macOS 0.83–0.87: PR stack and release tracker #3098
Position: 6 of 17.
Review base: 0.85-merge. Retarget as predecessors land; stable releases retain separate stable branches.
Current source: the PR's Commits tab tracks the latest repaired branch head.

Depends on #3033. RNM 0.85.0 with RN 0.85.3; retain a separate stable release branch.

Validation and backups

The branch-specific repaired source passed hardened immutable installation, constraints, and its complete release-helper selection. The selected 18-head packet records 1,406 passing helper tests. Exact source-tree equivalence is used for rewritten endpoints where applicable; the two changed linear RC checkpoints were tested separately.

Native/API evidence retains its recorded scope. The SwiftPM and RNTester repairs have six focused native build passes. Public stable versions and runtime/API contents were preserved except for the independently reviewed SwiftPM destination repair where applicable.

Public-registry lock correction passed all 18 hosted generation, hardened immutable, constraints, and metadata-audit jobs in run 35769816507. Only equivalent executable-path spelling changes are permitted; dependency versions, checksums, and ranges are unchanged. The previous functional test results remain applicable to this metadata-only correction. Fresh GitHub CI and review remain required. Previous heads are preserved on the same repository under backup/pre-ci-repair-20260922/<original-branch> and backup/pre-public-registry-20260922/<original-branch>; local complete-history bundles were verified as well.

The 0.87 PR sequence is one first-parent path: #3037 → #3104 → #3105 → #3106 → #3100 → #3101 → #3107. The redundant #3102/#3103 reviews are consolidated into #3105.

This section supersedes earlier stack order, source identity, and validation-status notes below.

Summary

Merge the pinned React Native 0.85-stable tip 2049278a5a76fbebf27b2b86f58ce865b673ba14 (0.85.3) into the certified React Native macOS 0.85 result dcd3d60324c220393aae7729bb538235f3c70416.

This is the separate 0.85 release line. It does not merge stable into mainline. Keep the PR based on temporary 0.85-merge; after the 0.85 merge lands, retarget optimistically to the future 0.85-stable.

Topology

Final head: c0432521ee7f67ac6082270a6e7d429a7c33f36d
Mechanical merge: f46b40d88327b1f8e2b24e863f022b17ff6a0309
Ordered parents: dcd3d60324c220393aae7729bb538235f3c70416, then 2049278a5a76fbebf27b2b86f58ce865b673ba14
Stable range: 59 commits after b5c815c1ca794ae5d1c0cb8b23e94418b7a4b140
Remote drift: none; fork and Microsoft 0.85-merge both remained at the certified parent

Conflict resolution

Initial Jujutsu state: 28 paths / 56 sides / 84 terms / 102 textual hunks / 0 deletion conflicts.

Class	Paths	Decision
Mechanical package/version metadata	20	Semantic three-way merge; preserve fork identities/workspace links and accept stable dependency changes.
Independent combine	2	Combine stable SwiftPM/WebSocket behavior with macOS platform source selection and nil-URL safety.
Generated	4	Hold the local lock baseline at the mechanical boundary, then regenerate Yarn/CocoaPods; take exact stable Hermes pins.
Structural rename/delete	1	Accept the stable RedBox split, then port AppKit behavior into extracted controllers and gate new UIKit-only V2 code.
Stale local	1	Remove redundant fmt tags and the duplicate Folly source now owned upstream.

Meaningful follow-ups:

Seed react-native-macos and @react-native-macos/virtualized-lists at 0.85.0-rc0; add a patch Changeset and exact react-native: 0.85.3 peers.
Preserve stable WebSocket provider injection inside the macOS nil-URL guard.
Port legacy RedBox AppKit UI to extracted files; disable UIKit-only RedBox V2/frame timing on macOS.
Pin Hermes V1 to 250829098.0.10 and recompose the standalone macOS framework into the universal XCFramework.
Restore Codegen absolute-path portability and exact release workspace/Metro versions under strict pnpm linking.
Compile exactly one legacy interop coordinator implementation per target.

Layered commits

f46b40d8 mechanical two-parent merge
d5e99e14 extracted RedBox macOS port
6864d743 Changesets release preparation
d17d2200 Yarn regeneration
0097d30f Hermes CocoaPods V1 mapping
5c41fcaa CocoaPods regeneration
77274e27 API snapshot regeneration
d01cf317 diff-tag correction
ea061efa release workspace versions
d3eb3f72 stable Apple feature gates
2618ca41 release dependency refresh
f4d0b4bc codegen snapshot regeneration
1538f9be Changesets base remote fix
2b57c6c8 Codegen path portability
87e71425 Metro stable alignment
0ed40f89 Metro lock refresh
ee2661e3 pinned/recomposed Hermes V1 prebuild
c0432521 legacy interop platform ownership

Validation

All final gates passed from a fresh exported Git checkout:

immutable Yarn install, constraints, yarn change:check, and yarn changeset status --since=upstream/0.85-merge
generated types/API and snapshots clean
282 Jest suites, 5,631 tests, and 1,826 snapshots
Flow, ESLint, Prettier, TypeScript, and generated TypeScript
iOS prebuild tests/syntax
Bundler/CocoaPods with deterministic lock topology
both Swift package dumps
isolated prebuild setup plus iOS, iOS simulator, macOS, visionOS, and visionOS simulator slices
RNTester macOS, iOS simulator, and visionOS simulator builds
exact DAG/parents, unique Change IDs, object connectivity, marker scan, trailers, and clean export

Evidence is under artifacts/release-stack/0.85-stable/, including the command transcript, per-hunk resolution ledger, layered commit map, diff-tag inventory, multiline-condition capture, and per-gate logs.

Diff-tag gate

The canonical guide remains byte-identical (79f533c26acf8e23bc2ea09d74d744aa16a1ed0b0ceecd026665af4a0f7d4d4c). The final scoped audit covers 72 paths: 29 tagged, 37 metadata/generated exemptions, 6 upstream-equal, and zero pairing, preprocessor-pattern, or macOS-file marker issues.

Independent judge requirement: re-audit the actual retained/new fork differences and full multiline conditions. Fail this execution for any untagged or mistagged difference, stale tag, missing file-level marker, or non-minimal rewrite of an upstream condition.

Complete conflict-path inventory

package.json
packages/babel-plugin-codegen/package.json
packages/community-cli-plugin/package.json
packages/dev-middleware/package.json
packages/eslint-config-react-native/package.json
packages/eslint-plugin-specs/package.json
packages/jest-preset/package.json
packages/metro-config/package.json
packages/react-native/Package.swift
packages/react-native/React/CoreModules/RCTRedBox.mm
packages/react-native/React/CoreModules/RCTWebSocketModule.mm
packages/react-native/gradle/libs.versions.toml
packages/react-native/package.json
packages/react-native/sdks/.hermesv1version
packages/react-native/sdks/.hermesversion
packages/react-native/third-party-podspecs/RCT-Folly.podspec
packages/react-native/third-party-podspecs/fmt.podspec
packages/react-native-babel-preset/package.json
packages/react-native-babel-transformer/package.json
packages/react-native-compatibility-check/package.json
packages/react-native-popup-menu-android/package.json
packages/rn-tester/Podfile.lock
packages/rn-tester/package.json
packages/virtualized-lists/package.json
private/helloworld/package.json
private/react-native-codegen-typescript-test/package.json
scripts/releases/ios-prebuild/configuration.js
yarn.lock

Final CI follow-up

Source validation is reused through exact tree equality:

No source-tree changes. The commit aligns this already-passing stable branch with its corrected mainline predecessor.

The complete 16-head batch passed 92 recorded validation commands, including branch-specific API revalidation/generated TypeScript, full formatting checks, and combined targeted suites where applicable. Native changes are limited to the reviewed #3033 destination guards (also present in stable 0.85) and #3104's sidecar-copy correction (already present in its descendants). Exact source equivalence preserves earlier native results elsewhere. The public-registry lockfiles and package manifests remain byte-identical.

Previous heads are backed up at backup/pre-ci-followup-20260922/<original-branch> on their source repository. Fresh current-head CI remains required. The one-first-parent 0.87 sequence is preserved.

The build_android workflow was incorrectly using for dry-run builds on stable branches (e.g., 0.85-stable), causing it to append suffix to the Hermes version. This resulted in trying to fetch non-existent SNAPSHOT artifacts like in https://github.com/facebook/react-native/actions/runs/22592250332/job/65471130298. This fix adds a check to detect stable branches (via github.ref_name or github.base_ref) and uses instead, which fetches the stable Hermes release from Maven Central without the -SNAPSHOT suffix. We check both github.ref_name and github.base_ref to cover two scenarios: ref_name: Direct pushes to stable branches (e.g. pushing to 0.85-stable) base_ref: Pull requests targeting stable branches (e.g. cherry-pick PRs where the source branch isn't named -stable but the target isChangelog: [Internal]

This reverts commit 111bd59.

This reverts commit 9f335b0.

#publish-packages-to-npm&next

Summary: Pull Request resolved: react#55925 Accidentally clobbered in D93247603. This affects the `fuseboxAssertSingleHostState` feature (react/react-native-devtools-frontend#218). Changelog: [Internal] Reviewed By: vzaidman Differential Revision: D95365621 fbshipit-source-id: 0df7f7bb33bb6bf6eabe15c8ee06c1761567c84b

Summary: Pull Request resolved: react#55613 The cloneMultiple method was written in a way to accept a list of families that are presumed to be owned by the api caller. This designe was mostly aimed at reanimated, that holds refernces to ShadowNodes (that own these families). In the case of AnimationBackend this didn't work properly, as when the view is unmounted we would lose the ShadowNodeFamily shared_ptr that we hold and it could get deallocated. Since now we can get an owning reference to ShadowNodeFamily from ShadowNode::getFamilyShared, we don't have to keep this old unsafe api. Instead we require the caller to have an owning reference with the api itself. This `cloneMultiple` method isn't really adopted in the community, so the breaking change shouldn't be a big problem. Changelog: [General][Breaking] - fix unsafe rawPointer access in cloneMultiple. Reviewed By: zeyap, javache Differential Revision: D93596770 fbshipit-source-id: c4d99b51875968ebce50358c19502cba02c50685

Summary: Pull Request resolved: react#55729 This is added so that one can easily enables c++ AnimatedModule in open source. If an app doesn't use `RCTAnimatedModuleProvider`(ios) or `AnimatedCxxReactPackage`(android), it can fallback to this default AnimatedModule when it has both c++animated and shared backend enabled - shared backend removes the need to pass down start/stop callbacks to NativeAnimatedNodesManagerProvider, so we can cleanly initialize it as static default - RCTAnimatedModuleProvider uses the version of AnimatedModule that still relies on a dedicated CADisplayLink for start/stop - AnimatedCxxReactPackage also bundles internal ViewEventModule (for NativeViewEvents) that shares `NativeAnimatedNodesManagerProvider` with AnimatedModule, but NativeViewEvents is not needed for open source - Alternatively we could also expose `NativeAnimatedNodesManagerProvider` via UIManager so other turbomodules can also use it. However I don't think it makes sense to double down on another animation API on UIManager given we have shared backend. - This assumes DefaultTurboModules is always the fallback module provider. So it'll not override when app already uses RCTAnimatedModuleProvider or AnimatedCxxReactPackage [General] [Added] - Add c++ AnimatedModule to DefaultTurboModules Reviewed By: NickGerleman Differential Revision: D94244698 fbshipit-source-id: 09e905eb4bad7d03cdf87d5b47352060b0e6212f

…into 0.85-stable

#publish-packages-to-npm&next

…t#56005) Summary: Pull Request resolved: react#56005 Changelog: [Internal] The build_debugger_shell CI job was failing because build-binary.js expects pkg.main to start with ./dist/, but without --prepack the prepack.js script never runs, so main stays as ./src/index.js. This was caused by a series of PRs: - PR react#54857 refactored debugger-shell/package.json to use the publishConfig pattern, moving main from ./dist/index.js to ./src/index.js. - PR react#55415 added the --prepack flag to build.js to support this. - PR react#55416 added the build_debugger_shell CI job but ran yarn build without --prepack. The fix passes --prepack to yarn build so that prepack.js rewrites package.json main to ./dist/index.js before build-binary.js runs. Reviewed By: huntie Differential Revision: D95818417 fbshipit-source-id: 03c8340c415960c3937b13bdea3952798d2d420e

Summary: Pull Request resolved: react#56100 ## Changelog: [iOS] [Fixed] - Revert RCTAnimatedModuleProvider change from D94244698 D94244698 added a guard in RCTAnimatedModuleProvider that returns nullptr when useSharedAnimatedBackend() is true, expecting DefaultTurboModules to handle AnimatedModule creation instead. However, on iOS the TurboModule resolution chain in RCTReactNativeFactory delegates to the app-provided getTurboModule:jsInvoker: and returns whatever the delegate returns — even nullptr — without falling through to DefaultTurboModules. This causes `Invariant Violation: Native animated module is not available` on any surface using Animated.View (e.g. Marketplace PDP) when react_fabric.enable_shared_animated_backend_ios is enabled. Revert the RCTAnimatedModuleProvider change from D94244698 so it always provides AnimatedModule when cxxNativeAnimatedEnabled is true, regardless of useSharedAnimatedBackend. The shared backend path in DefaultTurboModules still exists as fallback for non-iOS platforms. Reviewed By: christophpurrer Differential Revision: D96611917 fbshipit-source-id: e01cf5c80dc4cbf30afac6bcf414616c15bfaddb

#publish-packages-to-npm&next

Summary: When building React.XCFramework we build and link all source files in the XCFramework directly. To avoid Cocoapods to include the same files, we use a Ruby utility function called `podspec_sources` that will emit onlh header files when using (consuming) the build React.XFramework. When running RN-Tester after building it using the following pod install command line we have effectively linked with the prebuilt XCFrameworks instead of building from source: `# RCT_USE_RN_DEP=1 RCT_USE_PREBUILT_RNCORE=1 RCT_DEPS_VERSION=nightly RCT_TESTONLY_RNCORE_VERSION=nightly bundle exec pod install` The log in XCode will show an issue with duplciate symbols: ``` oobjc[2551]: Class _TtC10RCTSwiftUI23RCTSwiftUIContainerView is implemented in both xxxx/Library/Develope r/CoreSimulator/Devices/72157AA1-8D26-424E-8C2E-62D701E70B4A/data/Containers/Bundle/Application/3C711879-443E-48F1-B422-740E7AE82A74/RNTester.app/Frameworks/React.framework/React (0x108d3fb90) and xxx/Library/Developer/CoreSimulator/Devices/72157AA1-8D26-424E-8C2E-62D701E70B4A/data/Containers/Bundle/Application/3C711879-443E-48F1-B422-740E7AE82A74/RNTester.app/RNTester.debug.dylib (0x1039ef780). This may cause spurious casting failures and mysterious crashes. One of the duplicates must be removed or renamed. objc[2551]: Class _TtC10RCTSwiftUI18ContainerViewModel is implemented in both xxx/Library/Developer/CoreSimulator/Devices/72157AA1-8D26-424E-8C2E-62D701E70B4A/data/Containers/Bundle/Applicatio n/3C711879-443E-48F1-B422-740E7AE82A74/RNTester.app/Frameworks/React.framework/React (0x108d43b98) and xxx/Library/Developer/CoreSimulator/Devices/72157AA1-8D26-424E-8C2E-62D701E70B4A/data/Containers/Bundle/Application/3C711879-443E-48F1-B422-740E7AE82A74/RNTester.app/RNTester.debug.dylib (0x1039f0288). This may cause spurious casting failures and mysterious crashes. One of the duplicates must be removed or renamed. ``` This is because the RCTSwiftUI.podspec is missing using the `podspec_sources` function when setting up its source files: ``` s.source_files = "*.{h,m,swift}" ``` This will cause Xcode to both link with the XCFramework and compile the sources for this podspec once more - causing an app with duplicate symbols. After applying this fix, the same test as above shows no duplicate symbols. ## Changelog: [IOS] [FIXED] - Fixed duplicate symbol error when using React.XCFramework Pull Request resolved: react#56139 Test Plan: Run RN-Tester using the following pod install command line, causing us to link with the prebuilt XCFrameworks instead of building from source: `# RCT_USE_RN_DEP=1 RCT_USE_PREBUILT_RNCORE=1 RCT_DEPS_VERSION=nightly RCT_TESTONLY_RNCORE_VERSION=nightly bundle exec pod install` Build/run the app, observe that the duplicate symbol message is gone. Reviewed By: alanleedev Differential Revision: D97317019 Pulled By: cipolleschi fbshipit-source-id: 032113ad00890f712a6c70c3bd903f545f75aba1

Summary: Follow-up to - react#47033 - react#50431 TODO - [x] bump packages/react-native/third-party-podspecs/fmt.podspec - [x] bump scripts/releases/ios-prebuild/configuration.js - [x] packages/react-native/third-party-podspecs/RCT-Folly.podspec - [x] packages/react-native/gradle/libs.versions.toml - [x] packages/rn-tester/Podfile.lock - rn-rester (main) ios not building on Xcode 26.3, CI currently only supports Xcode 16 - i cannot downgrade macos26.4b4 locally to macos15 to install Xcode16.4 and bump pods this way - so on Xcode 26.3 i've attempted to bump only fmt minimally, ignoring remaining RN 0.86 hashes Ref: https://github.com/search?q=repo%3Afacebook%2Freact-native+%2211.0.2%22&type=code however unable to test rn-tester, ios doesn't seem to build on Xcode 26.3 let alone 26.4b not tested previous versions of Xcode not tested prior branches/tags to main rn-tester CI is passing on old macos-15 Xcode 16.4.0 only, ideally this should be extended to stable macos lts and Xcode 26.3 stable first separate follow-ups to this minimal fmt bump - bump CI macos-15 xcode 16.1-4 to macos-26 xcode 26.0-3 - bump rn-tester Podfile.lock from RN 0.82 to 0.86 main (aka nightly) - bump folly to 2025.11.03.00 - bump folly to 2026.03.09.00 Resolve: react#55601 [General][Changed] Bump fmt to 12.1.0 to fix Xcode 26.4 Pull Request resolved: react#56099 Test Plan: RNTester Reviewed By: alanleedev Differential Revision: D97358194 Pulled By: cipolleschi fbshipit-source-id: 3eb578a99a310e3eb77433692bf35502d0d78d24

#publish-packages-to-npm&next

…eact#56265) Summary: Pull Request resolved: react#56265 When an async void TurboModule method throws an NSException, performVoidMethodInvocation calls convertNSExceptionToJSError which accesses the Hermes JSI runtime from the native method call invoker thread. Since jsi::Runtime is not thread-safe, this causes heap corruption and EXC_BAD_ACCESS crashes across various hermes::vm::* functions. The sibling function performMethodInvocation was already fixed in D71619229 to re-throw the ObjC exception instead of converting to JSError when the call is async. This applies the same fix to performVoidMethodInvocation, which is always async. Related to SEV S641230 (4,550+ Hermes crashes in AMA iOS from OTA bundle 921191722). A JS change behind a QE/MC gate is triggering an NSException in a void TurboModule method for non-employee users, and this bug turns that into widespread memory corruption. This fix prevents the crash, but the triggering diff and throwing TurboModule still need to be identified separately. Matches upstream GitHub issue: https://github.com/facebook/hermes/issues/1957Commits affecting the React Native open source repository must have a changelog entry in the commit summary. Every React Native release has almost 1000 commits, and manually categorizing these commits is very time consuming. --- Changelog: [iOS][Fixed] - Fix Hermes crash when async void TurboModule method throws NSException by re-throwing instead of converting to JSError on wrong thread Reviewed By: javache Differential Revision: D98660782 fbshipit-source-id: bdedc769f17d9aec4156c45d0286c6c31ca006e4

…ct#56151) Summary: When building React Native (`0.85.0-rc.5`) core from source (`RCT_USE_PREBUILT_RNCORE=0`), the `React-Fabric/animated` CocoaPods subspec flattens the `event_drivers/` subdirectory headers because `header_mappings_dir` is not set. CocoaPods' `header_dir` without `header_mappings_dir` places all matched headers directly under the specified directory, losing any subdirectory structure. This means `event_drivers/EventAnimationDriver.h` ends up at `react/renderer/animated/EventAnimationDriver.h` instead of `react/renderer/animated/event_drivers/EventAnimationDriver.h`. The `#include` in `NativeAnimatedNodesManager.h` expects the full path with the `event_drivers/` subdirectory, so the build fails with: ``` 'react/renderer/animated/event_drivers/EventAnimationDriver.h' file not found ``` <img width="1512" height="1012" alt="Screenshot 2026-03-19 at 13 54 29" src="https://github.com/user-attachments/assets/49361c39-d48f-494f-ad7a-c9f3e9749a67" /> This doesn't affect prebuilt (`RCT_USE_PREBUILT_RNCORE=1`) builds because the xcframework ships with a VFS overlay that maps headers correctly. The fix adds `header_mappings_dir` to the `animated` subspec in `React-Fabric.podspec`, which tells CocoaPods to preserve the directory structure relative to `react/renderer/animated`. ## Changelog: [IOS] [FIXED] - Fix `EventAnimationDriver.h` not found when building React Native from source due to missing `header_mappings_dir` in `React-Fabric/animated` podspec Pull Request resolved: react#56151 Test Plan: 1. Set `RCT_USE_PREBUILT_RNCORE=0` in your Podfile 2. Run `pod install` 3. Build the project — previously fails with `'react/renderer/animated/event_drivers/EventAnimationDriver.h' file not found` 4. With this fix, the build succeeds Reviewed By: sammy-SC Differential Revision: D97295771 Pulled By: zeyap fbshipit-source-id: 945fbdeef1d25cedbec1e5b2d60c5a940da85840

…eact#56215) Summary: When testing React Native nightlies, we got the following error from `react-android-0.86.0-nightly-20260325-d1809f0aa-SNAPSHOT-release`: ``` StateWrapperImpl.h:14:10: fatal error: 'react/uimanager/StateWrapper.h' file not found ``` The reason is that build.gradle.kts exports src/main/jni/react/fabric → react/fabric/ in the prefab headers, which includes StateWrapperImpl.h. That header does #include <react/uimanager/StateWrapper.h>, but src/main/jni/react/uimanager is not in the prefab export list — so the header is missing from the AAR. This was introduced in react#55288 where they modified StateWrapperImpl.h to inherit from StateWrapper and added the #include on StateWrapper.h. This has caused Expo's nightlies to break due to the missing header file in the prefabs: - Internally (when RN builds itself): Works fine because all JNI source dirs are on the include path - Externally (when consumers use the published AAR): StateWrapperImpl.h is included in the prefab, it references <react/uimanager/StateWrapper.h>, but that header doesn't exist in the prefab package ## Fix This commit fixes the above problem by including `src/main/jni/react/uimanager` in the prefab. ## Changelog [Internal] - Pull Request resolved: react#56215 Test Plan: I have tested and verified this by running this in the root of the repo: ``` ./gradlew :packages:react-native:ReactAndroid:preparePrefab ls packages/react-native/ReactAndroid/build/prefab-headers/reactnative/react/uimanager/ ``` Before the fix the uimanager folder was not found, with the fix it exists and contains the following files: ComponentNameResolverBinding.h StateWrapper.h UIConstantsProviderBinding.h ## Changelog: [ANDROID] [FIXED] - Fixed missing StateWrapper.h header in prefabs ## Potential Issues There might be an issue with exporting these files in addition to the missing StateWrapper.h - but it seems like this is an issue with other folders in the jni / prefab - everything in a folder is exported when included for prefab. Reviewed By: alanleedev Differential Revision: D98124025 Pulled By: cipolleschi fbshipit-source-id: c8ae35e77652b90477d17ea8cab48ce3ee84d067

#publish-packages-to-npm&next

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Preserve the approved Changesets output, native versions, codegen snapshot, and CocoaPods lock. Apply the reviewed changelog correction where applicable.

Preserve validated per-branch source and corrected stack dependencies.

Preserve package versions and the linear stack; change only equivalent executable-path metadata.

Apply the independently reviewed branch-specific CI follow-up while preserving public-registry locks and the linear stack.

Alan Lee (alanleedev) and others added 30 commits March 2, 2026 09:40

Bump hermes version

4379f21

Introduce 'Determine Hermes build flag' step

111bd59

Revert "Introduce 'Determine Hermes build flag' step"

8ae042d

This reverts commit 111bd59.

Revert "[rn] Use stable Hermes for dry-run builds on stable branches"

c447fa1

This reverts commit 9f335b0.

[LOCAL] Do not use hermesNightly on the release branch

c35a22d

Release 0.85.0-rc.0

3e2367c

#publish-packages-to-npm&next

[LOCAL] Bump Podfile.lock

2750e60

[0.85] Add support for custom headers in devsupport (react#55976)

410ffb0

Merge branch '0.85-stable' of https://github.com/facebook/react-native …

9e1aaa8

…into 0.85-stable

Release 0.85.0-rc.1

6be3604

#publish-packages-to-npm&next

[LOCAL] Bump Podfile.lock

8f311e9

Release 0.85.0-rc.2

715336c

#publish-packages-to-npm&next

Release 0.85.0-rc.3

1c7c810

#publish-packages-to-npm&next

Release 0.85.0-rc.4

e2e415f

#publish-packages-to-npm&next

Release 0.85.0-rc.5

eae2c5f

#publish-packages-to-npm&next

[LOCAL] Bump Podfile.lock

5f9054b

Release 0.85.0-rc.6

8f22bbd

#publish-packages-to-npm&next

[LOCAL] Bump Podfile.lock

b3f24a5

Release 0.85.0-rc.7

b2839b1

#publish-packages-to-npm&next

Copilot AI and others added 17 commits September 21, 2026 01:17

chore(0.85): align release workspace versions

cd230b7

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

fix(0.85): gate stable Apple features on macOS

7253fc5

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

chore(0.85): refresh release dependencies

c7d0548

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

chore(0.85): regenerate codegen snapshots

84bf97a

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

fix(0.85): resolve Changesets base remote

8f3be4e

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

fix(0.85): transpile codegen sources from absolute paths

5f5a0ef

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

fix(0.85): align Metro stable dependencies

ead5611

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

chore(0.85): refresh Metro dependencies

f95dfc5

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

fix(0.85): pin Hermes V1 prebuild artifacts

a5ae959

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

fix(0.85): select one legacy interop implementation

621df23

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

chore: preserve Nx removal in 0.85 release metadata

be8be8b

chore(0.85): align the stable release graph

21bf07b

fix(macos): backport focused RedBox 2 support to 0.85 stable

fc9e72e

fix(0.85): apply reviewed validation artifacts and Hermes CI fixtures

27f62ec

chore(0.85): apply approved generated CocoaPods lock

dff695c

chore(0.85): prepare stable 0.85.0 release

dee4fa7

Preserve the approved Changesets output, native versions, codegen snapshot, and CocoaPods lock. Apply the reviewed changelog correction where applicable.

chore(0.85): refresh approved generated API snapshot

dfb67e7

Saad Najmi (Saadnajmi) force-pushed the 0.85/release branch from c043252 to dfb67e7 Compare September 21, 2026 14:53

Saad Najmi (Saadnajmi) force-pushed the 0.85-merge branch from dcd3d60 to 8b21f63 Compare September 21, 2026 14:53

This was referenced Sep 21, 2026

React Native macOS 0.83–0.87: PR stack and release tracker #3098

Open

feat: merge 0.85-merge into 0.84-merge #3033

Open

feat(macos): merge React Native through the RedBox 2.0 cutoff #3058

Open

Saad Najmi (Saadnajmi) changed the base branch from 0.85-merge to main September 22, 2026 16:05

Saad Najmi (Saadnajmi) changed the base branch from main to 0.85-merge September 22, 2026 16:05

fix(ci): apply reviewed release validation repairs

407d525

Preserve validated per-branch source and corrected stack dependencies.

Saad Najmi (Saadnajmi) changed the title ~~chore(0.85): merge up to 0.85.3 from upstream branch~~ chore(0.85): prepare stable 0.85.0 with React Native 0.85.3 Sep 22, 2026

Saad Najmi (Saadnajmi) added 4 commits September 22, 2026 12:06

fix(ci): align lock metadata with the public registry

685795d

Preserve package versions and the linear stack; change only equivalent executable-path metadata.

fix(ci): refresh validated snapshots and platform fixtures

88032ae

Apply the independently reviewed branch-specific CI follow-up while preserving public-registry locks and the linear stack.

fix(ci): refresh validated snapshots and platform fixtures

c7b8552

Apply the independently reviewed branch-specific CI follow-up while preserving public-registry locks and the linear stack.

fix(ci): refresh validated snapshots and platform fixtures

5162d0e

Apply the independently reviewed branch-specific CI follow-up while preserving public-registry locks and the linear stack.

Navigation Menu

chore(0.85): prepare stable 0.85.0 with React Native 0.85.3 - #3034

chore(0.85): prepare stable 0.85.0 with React Native 0.85.3#3034
Saad Najmi (Saadnajmi) wants to merge 89 commits into
microsoft:0.85-mergefrom
Saadnajmi:0.85/release

Saad Najmi (Saadnajmi) commented Jul 17, 2026 •

edited

Loading

Uh oh!

This branch has not been deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

19 participants

Conversation

Saad Najmi (Saadnajmi) commented Jul 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Current release stack

Validation and backups

Summary

Topology

Conflict resolution

Layered commits

Validation

Diff-tag gate

Complete conflict-path inventory

Final CI follow-up

Uh oh!

This branch has not been deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

19 participants

Saad Najmi (Saadnajmi) commented Jul 17, 2026 •

edited

Loading