refactor(rn): bump expo SDK to 56#65
Open
simeng-li wants to merge 1 commit into
Open
Conversation
Widen the expo-crypto / expo-secure-store / expo-web-browser peer caps to <57 to cover Expo SDK 55 and 56 (Expo realigned module majors with the SDK number, so the versions jump 15.x -> 55.x -> 56.x). Bump the dev deps and the sample app to Expo SDK 56 (RN 0.85, React 19.2).
There was a problem hiding this comment.
Pull request overview
Updates the React Native package’s Expo-module peer dependency caps and upgrades the included sample app to Expo SDK 56 (RN 0.85 / React 19.2), aligning this repo’s demo and development dependencies with the newer Expo/RN stack.
Changes:
- Bumped
@logto/rnversion to1.2.0and updated devDependencies to RN0.85.3+ Expo module56.x+@types/react ~19.2.0. - Widened
@logto/rnpeer dependency caps forexpo-crypto,expo-secure-store, andexpo-web-browserto<57(to include Expo SDK 55 and 56). - Upgraded
@logto/rn-sampleto Expo~56.0.9with corresponding RN/React/Expo module versions.
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| packages/rn/package.json | Bumps package version and adjusts dev + peer dependency ranges to support Expo module versions through <57. |
| packages/rn-sample/package.json | Upgrades the sample app dependencies to Expo SDK 56 / RN 0.85 / React 19.2. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Summary
Adds support for Expo SDK 56 (React Native 0.85, React 19.2) and bumps the sample app to it.
What changed
packages/rn— widened the peer caps forexpo-crypto,expo-secure-store, andexpo-web-browserto<57so the SDK supports Expo SDK 55 and 56. Lower bounds are kept (>=14.x), so existing SDK 52–54 consumers are unaffected. Bumped the matching dev deps to 56.x and@types/reactto~19.2.0. Version1.1.0 → 1.2.0.packages/rn-sample— upgraded the demo app to Expo SDK 56:expo ~56.0.9,react/react-dom19.2.0,react-native ~0.85.3,@expo/metro-runtime ~56.0.14,expo-status-bar ~56.0.4, and the three expo modules at56.x.Note on the cap value
Expo realigned module major versions with the SDK number starting at SDK 55, so these packages jump
15.x(SDK 54) →55.x(SDK 55) →56.x(SDK 56) — there is no16.x. That's why the cap is<57(covers 55 + 56) rather than<17.Verification
pnpm installresolves cleanly with no peer conflicts; confirmedexpo 56.0.9,expo-web-browser 56.0.5,expo-crypto/expo-secure-store 56.0.4,react-native 0.85.3,react 19.2.0.@logto/rn: build, type-check, lint, and unit tests pass; sample app type-checks.Testing
Tested locally
Checklist