- Update from previous version (data migration, no unnecessary logouts).
- Demo account (will Apple review be able to access most parts of the app if it requires login?)
- Release notes (every version should have different release notes)
- Visually check screenshots if they are up-to-date
- Create a branch
release/[version]
, where[version]
is the new build number to be released. - Commit and push changes. Send a pull request from
release/[version]
tomain
. - When merged, create a new tag on
main
with[version]
value. - Create a pull request from
main
todevelop
. - After merge, create new release on GitHub from
main
branch with semantic version tagx.y.z
. If continuous delivery is configured, release build and App Store submission will be processed automatically. - When build is processed to App Store Connect, let the tester go through it and ideally go through it yourself too.
- Only when tester approves the build, proceed with sending the update to the review.