what stackpulse tracks
Expo releases from GitHub
StackPulse watches Expo release notes and keeps the original source link close to every summary.
Open-source framework for universal native apps with React StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
what stackpulse tracks
StackPulse watches Expo release notes and keeps the original source link close to every summary.
upgrade risk
Risky changes are separated from normal feature notes so you can scan upgrade impact before changing production dependencies.
migration notes
Migration steps and recommended actions are only shown when the upstream release notes support them.
This patch release updates dependencies for expo-template-tabs. The listed dependency update is expo@58.0.25.
Users of expo-template-tabs are affected by the dependency update.
This patch release updates the default Expo template's dependencies. The listed dependency update is expo@58.0.25.
Users working with the default Expo template receive the updated expo dependency.
This patch release updates dependencies for the blank TypeScript Expo template. The listed dependency update is `expo@58.0.25`.
Users of the blank TypeScript Expo template receive an updated Expo dependency.
This patch release updates dependencies for the blank Expo template. The listed dependency update is to expo@58.0.25.
Users of the blank Expo template receive an updated Expo dependency.
Fixes an `Invalid state` error-level log on iOS and the corresponding warning on Android when `expo/fetch` cancels a response body. Cancellation before the first read now sets `bodyUsed`.
Users of `expo/fetch` on iOS and Android may see corrected logging and response-body state when cancelling before the first read.
This patch improves iOS Swift Package Manager builds for modules using checked-in Package.swift manifests, ensuring Expo macros, React Native headers, and generated app code are available through ExpoModulesCoreHeaders. It also fixes an incremental-build issue that could reuse stale ExpoModulesCore after precompiled headers change version, and updates dependencies.
Developers building Expo iOS modules with SwiftPM, particularly modules using checked-in Package.swift files, are affected by the build reliability and dependency changes.
This patch release switches environment-variable reading from `getenv` to `@expo/env`. It also updates dependencies, including `@expo/config-plugins`, `@expo/config`, and `@expo/env`.
Users of `patch-project` are affected by the environment-variable implementation change and dependency updates.
This patch release updates the Android Peek dependency to 0.3.3. It also updates dependencies, including @expo/ui to 58.0.28 and @expo/plist to 0.10.2.
Expo Widgets users, particularly on Android, receive the Peek dependency update and refreshed package dependencies.
This patch fixes Android browser-opening calls that could fail when App Links with `autoVerify` were configured for the same domain, by pinning the Custom Tab to a browser package. On iOS, source builds now use a checked-in `Package.swift` through the Expo SwiftPM plugin.
Android users opening browsers or authentication sessions for domains configured with App Links may be affected; iOS source builds also use the checked-in Swift package manifest.
This patch changes the iOS source build to use a checked-in `Package.swift` with the Expo SwiftPM plugin. The release notes describe no other changes.
The change affects iOS builds of expo-video-thumbnails when the module is built from source using the Expo SwiftPM plugin.
Fixes an iOS crash when playing a video with embedded artwork while `showNowPlayingNotification` is enabled and `metadata.artwork` is absent. Now Playing information uses plain values for the title, artist, and artwork instead of the asset’s `AVMetadataItem`s.
The fix affects iOS users playing videos with embedded artwork and Now Playing notifications enabled when no `metadata.artwork` is provided.
Update to expo-video 58.0.14 to receive the iOS crash fix.
Adds an asynchronous API for reading the advertising ID, avoiding the JavaScript-thread blocking caused by the synchronous Android API. Fixes importing the package on web: `isAvailable()` now returns `false` instead of triggering a missing native module error.
Expo Tracking Transparency users on Android can use the asynchronous API to avoid blocking the JavaScript thread, and web users can import the package without a missing native module error.
Consider using `getAdvertisingIdAsync` on Android when reading the advertising ID to avoid blocking the JavaScript thread.
This patch release fixes iOS `StatusBar` hidden and style changes not taking effect in apps built with the iOS 27 SDK. It also upgrades `react-native-safe-area-context` to 5.11.1 and updates several Expo dependencies.
Apps built with the iOS 27 SDK that use `StatusBar` hidden or style changes are affected by the fix; other users receive dependency updates.
This patch release replaces `glob` with Node’s `glob` for patch discovery. It also updates several Expo dependencies.
Users of `patch-project` are affected by the change to patch discovery and the updated dependencies.
This patch replaces glob-based detection of bridging headers with a filesystem path check. The release notes describe no other changes.
Users of install-expo-modules may be affected by the updated bridging-header detection; the notes do not specify further impact.
This patch replaces glob-based file discovery with filesystem directory listings and path checks. No other changes are described in the release notes.
Users of uri-scheme may be affected by the updated file-discovery implementation; no user-facing behavior changes are specified.
This patch mocks the `AssetRegistry` returned by `import { AssetRegistry } from 'react-native'`. This prevents `expo-asset` and `@expo/vector-icons` from failing with a missing asset registry module error.
Users testing projects that use `expo-asset` or `@expo/vector-icons` are affected by the asset registry mock fix.
This patch release upgrades `react-native-screens` to 4.30.1 and updates dependencies. The listed dependency versions include `expo@58.0.22` and `expo-router@58.0.29`.
Users of the Expo tabs template receive the updated `react-native-screens`, Expo, and Expo Router dependencies.
This patch release upgrades `react-native-screens` to 4.30.1 and updates several Expo package dependencies. The release notes describe dependency changes only, with no specific features, breaking changes, security fixes, or migration steps.
Expo 58.0.22 users receive updated `react-native-screens` and Expo package dependencies.
This release updates the `patch-project` package's dependencies. The listed dependency update is `@expo/config` to version 58.0.10.
Users of `patch-project` receive the updated `@expo/config` dependency.