Skip to content

chore: upgrade monorepo to Expo SDK 55#40

Draft
JoeSlain wants to merge 2 commits into
mainfrom
cursor/expo-sdk-55-upgrade-79dc
Draft

chore: upgrade monorepo to Expo SDK 55#40
JoeSlain wants to merge 2 commits into
mainfrom
cursor/expo-sdk-55-upgrade-79dc

Conversation

@JoeSlain
Copy link
Copy Markdown
Owner

@JoeSlain JoeSlain commented Apr 20, 2026

Description

Upgraded the Expo stack from SDK 54 to SDK 55 and aligned dependent React/React Native versions across the monorepo to avoid peer/version drift.

What changed

  • Upgraded apps/expo to Expo SDK 55 (expo, babel-preset-expo, Expo modules, RN ecosystem packages).
  • Upgraded apps/storybook-native to Expo SDK 55 and matching Metro preset.
  • Ran workspace version harmonization so shared packages and web/storybook apps use the same React/RN family versions.
  • Removed invalid Expo config key newArchEnabled from apps/expo/app.json to satisfy SDK 55 schema.
  • Updated lockfile after all dependency changes.

Type of Change

  • 🐛 Bug fix (non-breaking change which fixes an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • 📝 Documentation update
  • 🎨 Style update (formatting, renaming)
  • ♻️ Code refactoring
  • ✅ Tests update
  • 🔧 DevOps / Build config

How Has This Been Tested?

  • Manual testing

Commands run

  • npx expo@latest install expo@^55.0.0 --fix (in apps/expo)
  • npx expo@latest install expo@^55.0.0 --fix (in apps/storybook-native)
  • yarn check-deps:fix
  • yarn check-deps
  • npx expo-doctor@latest (in apps/expo) → 17/17 checks passed
  • Restarted and validated runtime services:
    • yarn web
    • yarn native
    • yarn storybook:web
  • HTTP/runtime probes:
    • curl -I http://localhost:3000
    • curl -I http://localhost:6006
    • curl -s http://localhost:8081/status

Checklist

  • My code follows the project's coding standards
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have updated the documentation (if applicable)
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

Screenshots (if applicable)

Next app after SDK 55 migration
Storybook manager after SDK 55 migration
expo_sdk55_upgrade_validation.mp4

Additional Notes

  • Storybook manager starts and is reachable; in this cloud environment the preview iframe remains spinner/loading (pre-existing behavior observed before this migration as well).
  • UI text/icon in the demo page still says “Expo SDK 54”; that is display content, not package version source of truth.

To show artifacts inline, enable in settings.

Open in Web Open in Cursor 

cursoragent and others added 2 commits April 20, 2026 12:06
Co-authored-by: Joe Slain <JoeSlain@users.noreply.github.com>
Co-authored-by: Joe Slain <JoeSlain@users.noreply.github.com>
@cursor cursor Bot changed the title chore(expo): upgrade app to Expo SDK 55 chore: upgrade monorepo to Expo SDK 55 Apr 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants