Upgrade to Expo SDK 55#48
Merged
Merged
Conversation
Bump expo to ~55.0.18 and run `expo install --fix` to align all SDK-managed peers (react 19.2.0, react-native 0.83.6, expo-* 55.x, eslint-config-expo 55.0.0, plus the gesture-handler / reanimated / screens / @types/react peers RN 0.83 requires). `expo-sharing` is registered as a config plugin in app.json — required in SDK 55. renovate.json's allowedVersions ceilings are slid to the SDK 55 line so Renovate keeps surfacing patch updates within-SDK and stops offering the SDK-coupled majors (eslint-config-expo is now in the same pin group as expo / @expo).
`react-native-reanimated@4` no longer bundles its worklets runtime; since SDK 55 it ships as a separate `react-native-worklets` package (found by `pod install` failing with `[Reanimated] Failed to validate worklets version` against expo-modules-core's RNReanimated.podspec). Pin to 0.7.x via renovate.json so it tracks the Expo SDK 55 line and won't drift independently.
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
This unblocks the ESLint v10 update path indirectly: ESLint 10 still needs `eslint-plugin-react` to ship its v10 fix (jsx-eslint/eslint-plugin-react#3979), but at least `eslint-config-expo` is now on the SDK-current major.
Background
Renovate offered `eslint-config-expo@55` (#36) and `eslint@10` (#35) standalone, but neither could merge — `eslint-config-expo@55` failed the `expo install --check` gate (SDK 54 expects `~10.0.0`), and `eslint@10` blew up at lint time because `eslint-plugin-react@7.37.5` still calls `context.getFilename()` (removed in ESLint 10). The clean way out is to bump the Expo SDK itself, which this PR does.
Test plan
CI-equivalent checks all green locally:
Pending verification (local-only — CI can't run iOS simulator)
Follow-ups
🤖 Generated with Claude Code