Files
Vojtech NovakandClaude Fable 5.1 1821e2f2cd [agent-cli] apps/eas-example moves to SDK 58 (llp/0030 §Delivery) (#136)
The prerequisite outside the llp/0030 stack: `apps/eas-example`, which
the live tier and the device-binding PRs dogfood, moves from SDK 57 to
SDK 58. Independent of #132 to #134.

## Why now

- `@expo/cli` 58 matches `run:android --device` by serial. The Android
instances of llp/0032 are read-only copies of one AVD that share a name,
so only the serial tells them apart.
- SDK 58 embeds the fingerprint that `status --explain` reads through
`expo-constants`; on 57 the installed app cannot be checked.
- The CLI targets SDK 58 and the 57 fallbacks are to be removed, so the
dogfood app should not keep exercising them.

## What changed

`expo install --fix` against SDK 58, with two versions held one patch
back by the repo's two-day minimum release age in `bunfig.toml`: `expo`
58.0.5 instead of 58.0.6 and `@expo/metro-runtime` 58.0.12 instead of
58.0.13. `expo install --check` reports only those two. A follow-up
bumps them once they clear the policy.

| Package | Before | After |
|---|---|---|
| expo | 57.0.19 | 58.0.5 |
| @expo/metro-runtime | 57.0.15 | 58.0.12 |
| expo-dev-client | ~57.0.18 | ~58.0.11 |
| expo-status-bar | ~57.0.1 | ~58.0.3 |
| react, react-dom | 19.2.3 | 19.3.0 |
| react-native | 0.86.3 | 0.88.0-rc.3 |

`expo config` resolves to `sdkVersion` 58.0.0. The lockfile follows.

## What to expect

- The fingerprint changes, so the local `live-eas` suite needs a
re-seeded finished build on EAS; the cloud-e2e workflow on this PR
builds its own dev client and proves the app on 58.
- No CLI code changes.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Fable 5.1 <[email protected]>
2026-10-08 16:13:34 +02:00
..