Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
@mrousavy this is awesome! As soon as you merge, I'll open a PR with Windows support 馃憤 |
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
2 participants
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.
Upgrade React Native Harness from 1.4.1 to 1.5.0, including the Android/Apple/UI packages, Bun and CocoaPods lockfiles, and both Harness workflows. The new GitHub Action runs setup and Metro cache steps through the installed CLI, so the action and package versions must stay aligned.
Reviewed the release notes and upstream changes for API migrations and removable workarounds. The new filesystem and platform Metro APIs do not require changes to our iOS/Android integration; the existing screenshot pixel assertions and Nitro runtime installation guard are still needed. There are no Harness package patches to remove.
Validation:
harness cicommands: both runner configurations, Metro restore planning, snapshotting, and save planning.NitroModules.createNativeArrayBuffer(...) reports external memory pressureassertion fails with-1049606instead of1048576. A cleanmainworktree with Harness 1.4.1 reproduces the exact same failure and pass count using the same native app (HarnessUI's native sources are identical between releases).Android runtime coverage will run in the existing PR CI matrix.