[dannyhw]

Brings the examples up to the latest Expo SDK 58 patch releases and updates the other dependencies that had safe minor or patch releases. Major-version updates are left for separate PRs.

Changes

Expo SDK 58 patches (all three Expo examples): expo-modules-core 58.1.0, expo-router 58.0.31, expo-updates, expo-sqlite, expo-constants, expo-font, expo-linking, expo-splash-screen, expo-status-bar, expo-symbols, expo-haptics, expo-web-browser, and babel-preset-expo 58.0.25 in the packages.

expo goes to 58.0.24, and expo-sqlite to 58.0.16. 58.0.25 and 58.0.17 were published today, so minimumReleaseAge blocks them. expo install --check lists only those two after this PR.

Published packages (changeset included):

• @storybook/react-native: tmcp 1.20, @tmcp/adapter-valibot 0.1.7, valibot 1.5, ws 8.22, glob 14.0.5
• @storybook/react-native-ui-common: es-toolkit 1.53
• @storybook/react-native-ui-lite: @legendapp/list 3.7.2

Tooling and examples:

• tsdown 0.23 and prettier 3.10.
• react-native-enriched-markdown 1.1.1 in ondevice-notes (dev) and the examples. The peer range stays ^1.0.2.
• @react-navigation/* in the router example.
• Re.Pack 5.4.3, Rspack 2.3, @rnx-kit/metro-config 2.2.6, react-native-test-app 5.4.17 and @swc/helpers in the repack example.
• vite 8.3 and @types/ws.
• pnpm dedupe.
• The repack Podfile.lock was still on Re.Pack 5.2.5; it now matches the installed 5.4.3.

Not updated:

• @tmcp/transport-http 0.9: @storybook/mcp still requires ^0.8.5, so updating it would install two copies.
• react-native-worklets, react-native-gesture-handler, @react-native-community/slider, @react-native-community/datetimepicker, react-native-svg: Expo SDK 58 pins the current versions.
• react 19.3.1: Expo SDK 58 and React Native 0.88.1 still expect 19.3.0.
• Major versions (Babel 8, ESLint 10, TypeScript 7, jotai 3, @changesets/cli 3, test-renderer 1.x, async-storage 3, ...): each needs its own migration.

Checks

pnpm build, test, check:types, lint, format:check and repo:lint pass.

tsdown 0.23 produces the same files as 0.22, except that @storybook/react-native now puts its shared runtime helpers in one extra small chunk.

Device testing

I rebuilt all four example apps from scratch for iOS (iPhone 17e simulator, iOS 27) and Android (Pixel 9 emulator, Android 15). On each app and platform:

• The device's story index matches the server's: 139 or 143 stories. expo-example shows 188 on the device and 180 on the server; the server's static parser misses 8 Button stories, the same gap as on next.
• Five stories render through select-story-sync.
• An updateStoryArgs round-trip works, with no error events.

App	iOS	Android
expo-example	✅	✅
expo-new-wrapper-example	✅	✅
expo-router-example	✅	✅
repack-example	✅	✅

In expo-example on both platforms, the Notes panel renders through react-native-enriched-markdown 1.1.1, including a syntax-highlighted code block. The Controls panel and live arg updates also work.

The MCP server (tmcp 1.20, valibot 1.5) returns all five tools. docs-list, docs-show and docs-show-story return content, and select-story changes the story on the device.

Notes for local builds

react-native-enriched-markdown downloads its code-highlight grammars in a postinstall script. This repo sets ignoreScripts, so run pnpm enriched-markdown:assets before expo prebuild (expo-example's prebuild, ios and android scripts already do this). Without it, pod install fails in the package's podspec. This is the same on next.

[changeset-bot]

🦋 Changeset detected

Latest commit: 02cf3d8

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 9 packages

Name	Type
@storybook/react-native	Patch
@storybook/react-native-ui-common	Patch
@storybook/react-native-ui-lite	Patch
@storybook/addon-ondevice-actions	Patch
@storybook/addon-ondevice-backgrounds	Patch
@storybook/addon-ondevice-controls	Patch
@storybook/addon-ondevice-notes	Patch
@storybook/react-native-theming	Patch
@storybook/react-native-ui	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR