npx @buildinternet/releases get expoRemoves temporary working directories after eas build:inspect copies inspect output, preventing leftover disk usage from failed builds. Also bumps several dependencies (tmp, ws, lodash, sigstore, axios, handlebars) to resolve Dependabot alerts.
Projects can now be deleted from the CLI via eas project:delete, and eas browse opens the project page on expo.dev in a web browser with optional subpage arguments. Also adds --dev-domain flag to eas deploy and -p alias for --platform in eas simulator:start.
Removed the eas onboarding command (and its init:onboarding, project:onboarding aliases). The eas workflow:create command is significantly improved with a --template flag, shorter default file names, automatic EAS Build/Update configuration, and automated dev-client installation. Also added seven PostHog workflow functions, rethrew Apple errors during capability sync, and retries asset uploads during eas update instead of failing.
Passkeys can now be added to Expo accounts and used as a primary authentication factor, replacing the password-plus-OTP combination. Users with 2FA enabled can sign in with a passkey directly, skipping the second step. Passkeys are managed at expo.dev/settings#sign-in-methods and are unavailable to SSO users.
Free plan users no longer see warnings about reaching their build limit while still well below it; overage warnings now only show for paid plans with actual billable overage. Fixed tvOS build target selection for non-interactive Apple builds when EXPO_TV env variable is set.
Upgrades from React Native 0.85 to 0.86, a release intended to have no breaking changes. Expo prebuild now clears and regenerates native android/ios directories by default. Also includes improvements to edge-to-edge Android support, DevTools dark mode, expo-image cache APIs, and animation library bumps.
Introducing a new insights dashboard, showing you how every Maestro end-to-end test run performed over time, across your whole team. Identify flakey tests, see when regressions were introduced, and stop scrolling through endless logs.
There are several ways to distribute iOS apps to your team: for devices, you can use TestFlight, ad hoc provisioning, or enterprise provisioning, and for simulators you can share a direct link to the build that can be installed manually or through…
Connect your AI coding assistant to your Expo project from any Expo plan.