Repository navigation
chore(mobile): bump app version to 2.3.0 - #7914
Merged
Merged
Conversation
ronishrohan
approved these changes
Nov 7, 2026
Contributor
🏆 Review leaderboardOct 31, 2026–Nov 7, 2026 · UTC
Ranked by distinct external PRs reviewed, then review rounds, then PR comments. Self-activity and bot activity are excluded. Show 8 more reviewers
|
3 of 4 tasks
6 tasks done
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.2.0 to 2.3.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.3.0 is the first store build with the native overhaul (#7836–#7839), mobile Sentry (#7470) and the iPad hardware-Return module (#7666). None of them can ship to 2.2.0 users as an OTA, so they need a new store release.
Before / After
main: iOSee5379ff…, Androidf99ab5a4…52a442a3…, Android4980814e…The app version is part of the Expo fingerprint, so this bump also moves the runtime. That's expected for a store release: OTAs published from this tree target 2.3.0 builds only.
How
One line, as in #6602 and #7396. The
2.2.0@42strings inlib/sentry.test.tsare test fixtures, not the app version, so they stay.Testing
npx vitest run: 360 files and 3,487 tests pass.npx expo-updates runtimeversion:resolve --platform ios|androidon a clean tree, before and after, gives the runtimes above.mainatf8c84e393d, the same tree plus this one line, was tested with Release builds:Checklist
main(or continuing an existing PR branch)go, frontend, etc.)