{"id":"6aef7c0a36b42f63f0fc669e","title":"2026 11 07 Issue 151 Increase The App Store Version Automatically After Each Sale","path":"how-to/committee/release-notes/2026-11-07-issue-151-increase-the-app-store-version-automatically-after-each-sale","contentMarkdown":"# 07-Nov-2026 — increase the App Store version automatically after each sale [#151](https://github.com/Ramblers-GB/ngx-ramblers/issues/151)\n\n## [build 1068](https://github.com/Ramblers-GB/ngx-ramblers/actions/runs/42405560252) — [commit 93eaadd](https://github.com/Ramblers-GB/ngx-ramblers/commit/93eaadd87e52abba778841ece4d3b0be7fc95a25)\n\n_____\n\n## What's new\n\n- You no longer choose when the iPhone app gets a new store version. After each successful website build on `main`, the native job uploads a fresh iPhone binary and submits it for Apple’s App Review. When Apple approve it, that version is released on the App Store.\n- If the current version is already on sale, the job uses the next number (for example 1.1 then 1.2). If a version is already with Apple, the job leaves that review alone.\n- TestFlight is not used. Walkers install and update from the App Store.","contentHtml":"07-Nov-2026 — increase the App Store version automatically after each sale #151
\n\n
\nWhat's new
\n\n- You no longer choose when the iPhone app gets a new store version. After each successful website build on
main, the native job uploads a fresh iPhone binary and submits it for Apple’s App Review. When Apple approve it, that version is released on the App Store. \n- If the current version is already on sale, the job uses the next number (for example 1.1 then 1.2). If a version is already with Apple, the job leaves that review alone.
\n- TestFlight is not used. Walkers install and update from the App Store.
\n
\n"}