From 5aa50bd9c455aeadfc0a7d4b55da437664502d89 Mon Sep 17 00:00:00 2001 From: Daniel Dimitrov Date: Mon, 23 Dec 2024 08:46:51 +0100 Subject: [PATCH] docs(mobile): add release procedure docs --- apps/mobile/docs/release-procedure.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 apps/mobile/docs/release-procedure.md diff --git a/apps/mobile/docs/release-procedure.md b/apps/mobile/docs/release-procedure.md new file mode 100644 index 0000000000..6868b7c00b --- /dev/null +++ b/apps/mobile/docs/release-procedure.md @@ -0,0 +1,15 @@ +# Releasing to Production + +The code is being actively developed on the `main` branch. Pull requests are made against this branch. + +When we want to make a release, we create a new branch from `main` called `mobile-release/vX.Y.Z` where `X.Y.Z` is the +version number of the release. + +This will trigger a new build on the CI/CD pipeline, which will build the app and submit it to the internal distribution +lanes in App Store and Google Play Store. + +The release has to be tested by QA and once approved can be promoted to the production lane. + +## Triggering Maestro E2E tests + +On the release PR add the github label `eas-build-ios:build-and-maestro-test` to trigger the e2e tests in Expo CI.