[0.87] Stamp the React Native version in prebuilt iOS core artifacts

[cipolleschi]

Target Branch

0.87

Link to commit or PR to be picked

react/react-native@95df500

Description

This fixes a build-breaking issue in the prebuilt iOS core artifacts. The compose job currently ships ReactNativeVersion.h with the 1000.0.0 development sentinel even though the compiled binary and npm package have the correct release version. With the materialized prebuilt headers used by 0.87, third-party libraries read this incorrect header and compile the wrong version-gated code paths.

For example, react-native-unistyles sees REACT_NATIVE_VERSION_MINOR as 0, selects a removed pre-0.81 API path, and fails to build with a shadowNodeFromValue error. This affects consumers of the prebuilt React Native core and makes the artifact internally inconsistent.

The fix composes ReactNativeVersion.h from the already-stamped headers produced by the slice build, while continuing to source every other header from the compose checkout. It also invalidates pre-fix caches and adds a verification gate that prevents release or nightly artifacts from shipping the development sentinel again.

This is appropriate for 0.87 because it fixes the correctness of the release artifact and restores compatibility with third-party libraries, matching the support policy criteria for bugs in the core React Native experience and APIs used by third-party libraries.

Validation covered local composition, the sentinel detection gate, a fresh React Native nightly app with react-native-unistyles@3.3.0 on Xcode 26.3 in prebuilt mode, and the Expo prebuilt harness on Xcode 26.3 and 26.6. Stock artifacts reproduced the failure; the correctly stamped header resolved it.

[github-actions]

Thank you for opening a new React Native Pick Request.

These are the criteria we follow when accepting or rejecting a code change into a React Native release branch (source).

If your Pick Request does not satisfy the criteria below, please close it as it will not be considered.

✅ Which Pick Requests we accept

1. ✅ Fixes for regressions to core APIs. Examples:
   • A core component is behaving differently between versions 0.X and 0.X-1
   • The TurboModule.getEnforcing function is throwing an unexpected assertion error.
2. ✅ Fixes to bugs in core React Native. Examples:
   • Breakpoints in React Native DevTools not working correctly in the debugger
   • Fast Refresh not working as expected
   • Metro bundler not starting properly or ignoring the configuration file
   • Buttons that are not clickable
3. ✅ Fixes to APIs used by third-party libraries and out-of-tree platforms. Examples:
   • An API used by react-native-macos is not behaving as expected or is regressing
4. ✅ Bump of patch version of dependencies. Example:
   • Bump Gradle from 8.11.0 to 8.11.1
5. ✅ Fixes for low/high severity security vulnerabilities. Example:
   • Bump Gradle from 8.11.0 to 8.12.0 if there is a security vulnerability in 8.11 and no 8.11.x version contains the same fix.
6. ✅ Fixes and reverts of accidental breaking changes. Example:
   • Reverting or fix-forwarding a Kotlin migration of a file (e.g. ReactRootView.java) if it is causing a breaking change for the React Native ecosystem.
7. ✅ Performance improvements. Examples:
   • Fixing unnecessary re-renders in FlatList.
8. ✅ Any Pick Request if the release is still in RC0 (after RC1, the previously listed criteria apply)

❌ Which Pick Requests we don't accept

9. ❌ Any Pick Request that introduces a breaking change after RC1. Example:
   • A bugfix that contains a refactoring, resulting in changes to the public API of a class
10. ❌ Any Pick Request that introduces a new feature after RC1. Example:
    • A commit that introduces a new API or a specific feature for a component.
11. ❌ Bump of major or minor version of dependencies. Examples:
    • Bump Gradle from 8.11.0 to 8.12.0
    • Bump Gradle from 8.11.0 to 9.0.0
12. ❌ Bump of a dependency to a pre-release version. Example:
    • Bump Gradle from 8.11.0 to 8.11.1-beta.1
13. ❌ Any Pick Request that introduces changes to the React Native testing infrastructure after RC1. Examples:
    • Changes to GitHub Actions workflows to optimize them, even if they are on main.
    • Changes to the logic used to publish packages to NPM or Maven Central
14. ❌ Pick Request composed of multiple commits that have several merge conflicts.
    • If your Pick Request is too complex to apply to the release branch, it will be rejected.
15. ❌ Any non-critical improvement that landed on main.
    • These will generally ship in the following version unless they fit one of the criteria above.
16. ❌ Any Pick Request considered a "nice to have".
    • Even one-line changes carry a risk of destabilizing and further delaying the release.

ℹ️ What makes for a good Pick Request

In order for your Pick Request to be considered, please do the following:

• ℹ️ Limit your Pick Request to one commit from main, or one PR against the release branch.
• ℹ️ Include a clear explanation of why your Pick Request should be considered, ideally referencing one of the criteria above.
• ℹ️ Target only one minor version of React Native (e.g. [0.76]). To have your Pick Request applied to more versions, please open separate Pick Requests.

[zeyap]

@react-native-bot merge 95df50034ba5ce11f4b70bbb6bf692e3691297dc 0.87-stable

[react-native-bot]

✅ Successfully picked up your commit react/react-native@95df500 on the branch https://github.com/facebook/react-native/commits/0.87-stable