26 Expo SDK 55 packages are behind their expected versions

[kmch4n]

Summary

npx expo install --check reports 26 packages behind the versions Expo SDK 55 expects, including react-native itself.

expo@55.0.17                  -> ~55.0.30
expo-constants@55.0.15        -> ~55.0.17
expo-crypto@55.0.14           -> ~55.0.19
expo-dev-client@55.0.28       -> ~55.0.39
expo-device@55.0.15           -> ~55.0.21
expo-file-system@55.0.17      -> ~55.0.26
expo-font@55.0.6              -> ~55.0.8
expo-glass-effect@55.0.10     -> ~55.0.11
expo-haptics@55.0.14          -> ~55.0.18
expo-image@55.0.9             -> ~55.0.11
expo-image-picker@55.0.19     -> ~55.0.24
expo-linking@55.0.14          -> ~55.0.17
expo-localization@55.0.13     -> ~55.0.19
expo-media-library@55.0.15    -> ~55.0.21
expo-router@55.0.13           -> ~55.0.18
expo-sharing@55.0.18          -> ~55.0.24
expo-splash-screen@55.0.19    -> ~55.0.25
expo-sqlite@55.0.15           -> ~55.0.20
expo-status-bar@55.0.5        -> ~55.0.6
expo-symbols@55.0.7           -> ~55.0.9
expo-system-ui@55.0.16        -> ~55.0.22
expo-video@55.0.15            -> ~55.0.21
expo-video-thumbnails@55.0.14 -> ~55.0.19
expo-web-browser@55.0.14      -> ~55.0.20
react-native@0.83.6           -> 0.83.10
eslint-config-expo@55.0.0     -> ~55.0.1

All are patch-level moves inside SDK 55 — no major version change is involved.

Why this is not being done automatically

npx expo install --fix applies all of it in one command, so the change itself is trivial. The verification is not:

• It touches package-lock.json and every native module the app depends on, including expo-sqlite, expo-media-library and expo-video, which sit under the import, thumbnail and playback paths.
• SnowLog needs an EAS dev build to run at all (SDK 55 is not supported by Expo Go), so this cannot be validated from a workstation. It needs a fresh build and a walk through migrate → import → search → export on a device.
• There is no CI, so npm run lint and npx tsc --noEmit passing locally is the whole automated signal.

Deciding when to absorb that — and whether to do it as its own change or fold it into the next release — is a maintainer call.

Suggested handling

1. Run npx expo install --fix on a branch or immediately before a release build.
2. Rebuild the dev client and walk the database path end to end from a clean install.
3. Re-run npm run lint, npx tsc --noEmit, node --test "scripts/tests/*.test.cjs".
4. npx expo-doctor for anything the version check does not cover.

Acceptance criteria

• npx expo install --check reports no outdated packages.
• Import, thumbnail generation, search and export verified on a device after the bump.