Repository navigation
chore(mobile): bump app version to 2.4.0 - #8337
Merged
Merged
Conversation
Contributor
🏆 Review leaderboardNov 6–13, 2026 · UTC
Ranked by distinct external PRs reviewed, then review rounds, then PR comments. Self-activity and bot activity are excluded. Show 7 more reviewers
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Code changes: +0 -0
Tests: +0 -0
Others: +1 -1
What
Bumps the mobile app version from 2.3.0 to 2.4.0 in
packages/mobile/app.json, ready for the next store build. Build numbers stay with EAS (appVersionSource: "remote",autoIncrementon the production profile).Why
2.4.0 is the first store build with native changes that 2.3.0 users can't get as an OTA:
expo-video,react-native-pdf-renderer,expo-asset).Before / After
main(d331675e53): iOSc22fdede…, Androidf44fd649…871a9935…, Androidd5ab2ee7…The app version is part of the Expo fingerprint (
runtimeVersion.policy: "fingerprint"), so this bump also moves the runtime. That's expected for a store release: EAS computes the same runtime when it builds this tree, and OTAs published from it target 2.4.0 builds only. No other runtime or build-number settings need to change.How
One line, as in #7914. Nothing else in
packages/mobilenames the app version outside test fixtures.Testing
npm run typecheckandnpx vitest runinpackages/mobile: 436 files, 4,215 tests pass.npx expo-updates runtimeversion:resolve --platform ios|androidon a clean tree (noios/,android/orgoogle-services.json), before and after, gives the runtimes above.mainatd331675e53(this tree minus the version line), installed side by side with OTA off on a Pixel 10a (Android 17) and an iPhone 17 Pro Max (iOS 27.2). Both install and launch.Pixel 10a, on validated home Wi-Fi:
Earlier RC passes on the Pixel, from
bd4d0d4540onwards, also covered the artifact viewers (video, audio, PDF, CSV, Mermaid, ZIP), Files with branch and changes pickers, the PR list, New task, local project creation, chat and terminal.iPhone, still to be confirmed by hand: #8331 both ways, #8281 (switching to All machines draws full-width rows), #8285, #8286 (closing the sign-in sheet, then signing in again), and no false offline banner.
Known, not in this release: on a Wi-Fi network Android can't validate (seen on an iPhone hotspot), a machine stays "Phone offline" after the phone comes back online, until the app is restarted (follow-up to #8282). Validated networks recover as above.
Checklist
main(or continuing an existing PR branch)go, frontend, etc.)Summary by CodeRabbit