Skip to content

v1.3.0

Latest
Latest

Choose a tag to compare

View all tags
@simeng-li simeng-li released this 10 Sep 09:40
v1.3.0
384d285
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Summary

  • Add Expo SDK 57 support to @logto/rn. On npm the previous <57 peer cap was a hard ERESOLVE install failure for every SDK 57 project, so this unblocks installing the SDK at all on the current Expo release.
  • Default the dev setup and sample app to Expo SDK 57.
  • No source changes — the SDK code itself is unaffected by the Expo 57 bump.

Changes

Expo SDK 57 support (#69)

  • Widen peerDependencies in packages/rn/package.json so @logto/rn supports Expo SDK 52–57 — expo-crypto, expo-secure-store, and expo-web-browser are now allowed up to <58.
  • Bump dev dependencies to Expo SDK 57 defaults (react-native 0.86.3, expo-secure-store 57.0.3).
  • Update the sample app in packages/rn-sample/package.json to Expo SDK 57 (expo 57.0.21, @expo/metro-runtime 57.0.15, react/react-dom 19.2.3, react-native 0.86.3), matching Expo 57.0.21's bundledNativeModules.
  • Pin react-native exactly rather than with ~, matching Expo's own template. A tilde range lets React Native float to a newer patch than the resolved expo expects, which expo-doctor then flags as a version mismatch.

Docs (#67)

  • Align the README logo with current Logto branding, with light and dark variants.

Upgrade Notes

  • Projects on Expo SDK 52–56 remain supported; no changes are required to stay on your current SDK.
  • Expo SDK 57 users on npm should now be able to run npm i @logto/rn without ERESOLVE, and no longer need --legacy-peer-deps as a workaround.
  • After upgrading, reinstall dependencies and rebuild to pick up the updated native SDK versions.

Full changelog: v1.2.0...v1.3.0

Assets 2
Loading