Repository navigation
feat: support every stable New Architecture React Native release (2.0.1) - #8
Merged
Merged
Conversation
RN 0.88.0 became npm latest on 2026-10-15 and was rejected by the `<0.88.0` peer cap. Remove the RN and React peer upper bounds and declare support for every stable RN release with the New Architecture from 0.76. - Android: use the non-deprecated six-argument ReactModuleInfo constructor (available from RN 0.73); keep TurboReactPackage until the floor reaches 0.74, where BaseReactPackage exists. - Native CI: per-release toolchains in matrix.json (SDK/NDK, macOS runner, Xcode). PR lanes RN 0.88.0/0.87.1; weekly/manual window lanes RN 0.82.1/0.78.3/0.76.9, with 0.76/0.78 iOS on Xcode 16.4 because their bundled fmt does not compile with newer Xcode. - Add a scheduled release monitor that fails when npm latest is newer than the newest lane; it never gates pull requests. - Contract tests reject capped peers and require lanes from the 0.76 floor to the newest release. - Bump to 2.0.1 and document the support policy and local lane evidence. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
React Native 0.88.0 became npm
lateston 2026-10-15. The 2.0.0 peer rangereact-native >=0.73.0 <0.88.0rejects it, so a fresh RN app getsERESOLVEon install, and every new RN minor release would do the same.What
react-native >=0.73.0,react >=18.2.0. Supported: every stable RN release with the New Architecture from 0.76. 0.73–0.75 and Old Architecture stay best effort.ReactModuleInfoconstructor, which is not deprecated and exists from RN 0.73.TurboReactPackageis kept on purpose:BaseReactPackageonly exists from 0.74. Checked against the 0.89 nightly of 2026-10-16: still present, deprecation at warning level only.matrix.jsonnames its SDK/NDK and macOS runner/Xcode.stable(every PR): 0.88.0, 0.87.1window(weeklysupportschedule / manual): 0.82.1, 0.78.3, 0.76.9. iOS 0.76/0.78 usemacos-15/ Xcode 16.4 because their bundledfmtfails with aconstevalerror on newer Xcode. This is upstream and also affects apps that don't use this package.latestis newer than the newest lane. It is not part of the required check.Local evidence (before commit)
fmtfailure; package compiles/links withfmtpatched (diagnostic only)fmtfailure; package compiles/links withfmtpatched (diagnostic only)Before merge / release
stablerun green on this PRsupportrun green (firstmacos-15/ Xcode 16.4 lanes)docs/release-readiness.md(npm publish not done)🤖 Generated with Claude Code