ci: bump Expo SDK 57 packages to expected patch versions - #88
Merged
Conversation
The Quality-checks job runs `npx expo install --check`, which started failing on every PR after Expo shipped patch releases within SDK 57: the pinned versions drifted from what the installed expo expects, so the step exited 1 and blocked all CI. Bring the nine drifted packages to their expected patch versions (expo 57.0.7 -> 57.0.8, expo-router, expo-dev-client, expo-linking, expo-splash-screen, expo-build-properties, expo-constants, expo-web-browser, react-native-screens). All within SDK 57 — no minor/major changes. Verified: `expo install --check` clean, `npm ci` clean, typecheck clean, 231 tests pass.
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.
Why
The Quality checks job runs
npx expo install --check, which started failing on every PR (27s red) after Expo shipped patch releases within SDK 57. The pinned versions drifted from what the installedexpoexpects, so the step exits 1 (Found outdated dependencies) and blocks all CI — unrelated to whatever a given PR actually changes.Fix
Bring the nine drifted packages to their SDK-57 expected patch versions — all within SDK 57, no minor/major bumps:
package.json+package-lock.jsononly.expo install --fixalso wanted to reformatapp.jsonand add anexpo-web-browserconfig plugin; I reverted that so this stays a pure dependency fix and introduces no native-config change.Verified
npx expo install --checkclean ·npm ciclean · typecheck clean · 231 tests pass.