React Native v0.79.5 (v0.79.4 & v0.79.3)#172
Merged
kraenhansen merged 2 commits intomainfrom Jul 12, 2025
Merged
Conversation
added 2 commits
July 12, 2025 16:37
kraenhansen
added
Apple 🍎
🦋 Changeset detectedLatest commit: 796241f The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR adds support for React Native versions 0.79.3, 0.79.4, and 0.79.5, building on previous work that removed the Hermes version pinning. The changes update peer dependencies and upgrade the test application to use the latest supported version.
- Expands peer dependency range to include React Native 0.79.3-0.79.5
- Updates test app and root package to use React Native 0.79.5
- Adds changeset documentation for the version support expansion
Reviewed Changes
Copilot reviewed 4 out of 5 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| packages/host/package.json | Expands peerDependencies to accept React Native 0.79.3-0.79.5 |
| package.json | Updates root React Native dependency from 0.79.1 to 0.79.5 |
| apps/test-app/package.json | Updates test app React Native dependency from 0.79.1 to 0.79.5 |
| .changeset/ten-parts-check.md | Documents the React Native version support changes |
Collaborator
Author
|
Merged to get the example repo public without peer dependency warnings, please review in retrospect 🤞 |
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
1 participant
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.
With #158 merged we're no longer pinned to a specific version of Hermes.
I've pushed a tag for the 0.79.3 cut of Hermes (also used by 0.79.4 and 0.79.5 - which is default for the latest version of Expo SDK 53) with the Node-API patch on-top:
node-api-hermes-2025-06-04-RNv0.79.3-7f9a871eefeb2c3852365ee80f0b6733ec12ac3b
Merging this PR will: