Summary: How the 7Mind mobile app (7mind-mobile-apps-monorepo) ships to the App Store and Google Play: a GitHub release from main, Codemagic production builds from main, then store review and a phased rollout. Sources: Notion extraction 2026-05-15 (New 7Mind Release Process, New Release Process, Releasing 7 Mind 3.0.x); on 2026-11-09 the repo doc documentation/docs/sevenmind/deployment.md, .github/workflows/release_drafter.yml, .github/release-drafter.yml, .github/workflows/nightly_e2e.yml, codemagic.yaml (origin/main at 4.0.9) and gh release list (v4.0.0 to v4.0.9) Last updated: 2026-11-09


Cadence

The Notion process sets Thursday as release day. The role rotates and is called the “Release Guru” (rotation maintained in Notion). The default is one release per two weeks, with exceptions for urgent bug fixes that ship out of cycle. In practice the recent releases came about weekly, on Thursdays and Fridays: 4.0.5 on 8 October, 4.0.6 on 22 October, 4.0.7 on 30 October, 4.0.8 and 4.0.9 on 6 November 2026.

Pipeline Overview

The mobile app lives in the 7mind-mobile-apps-monorepo repo. The steps follow the repo doc documentation/docs/sevenmind/deployment.md.

  1. Release on GitHub. Run the GitHub Actions workflow release-drafter (.github/workflows/release_drafter.yml) by hand on main. Every push to main keeps a draft release up to date, with the merged PR titles grouped by label. The manual run publishes that draft as release X.Y.Z, which creates the tag vX.Y.Z, then commits “updated: version to X.Y.Z” to pubspec.yaml and pushes it to main. The version is a patch bump unless a PR carries a major or minor label.
  2. Build in Codemagic. Start “iOS Workflow Production” and “Android Workflow Production” on the main branch. Build from main, not from the tag: the tag points at the commit before the version bump, so a build from the tag carries the previous version. Build numbers are incremented automatically from App Store Connect and Google Play.
  3. Watch the builds in the Slack channel #internal-releases-mobile-apps (start, success and failure).
  4. iOS. Codemagic uploads the build to TestFlight for the “Internal Testers” group; internal testers are notified. It does not submit to the App Store.
  5. Android. Codemagic uploads the AAB to the Google Play internal track as a draft. Add the change log and publish the draft by hand so internal users get the release.
  6. Release notes. If the release only contains bug fixes, use “Bug fixes and improvements”. If it has new features, request the text from Dana, then request translations in #translations-requests.
  7. Submit the new version for review in App Store Connect and Google Play, then roll it out (see below).
  8. The Release Guru posts a release message in #releases-7mind-flutter, based on the GitHub release notes.

If Codemagic is down, or a release candidate is needed without publishing, deployment.md also describes a fully manual build: Android signed with the keystore from the Android vault in 1Password, iOS archived with flutter build ipa and uploaded with Apple’s Transporter app.

Phased Rollout

Releases go out in phases:

  • iOS: phased release through App Store Connect.
  • Android: phased rollout, brought to 100% over roughly a week.

Code Freeze and Branching

There are no release branches. release-drafter tags main and Codemagic builds main, so a release contains everything merged to main before the release-drafter run. Unfinished features ship dark behind a ConfigCat or Braze flag (see mobile-analytics-stack). The repo does not write down a code freeze rule.

Testing Strategy

  • Unit tests on bloc, repos, services, managers, extensions, models: make ci_test in the GitHub Actions workflow test.yml on every PR and main push, with Codecov. The Codemagic staging, ZPP and Android production workflows run them again before building; the iOS production workflow skips them.
  • Patrol e2e tests live in the monorepo (integration_test/). They run every night against the staging flavor: the GitHub Actions workflow nightly_e2e.yml (03:00 UTC) starts the Codemagic workflows e2e-tests-android-workflow and e2e-tests-ios-workflow, which run the suite on Firebase Test Lab and fail on a failing test. Results land in #internal-releases-mobile-apps. See mobile-build-pipeline.
  • Subscription flow smoke tests (purchase, restore, dunning) before promoting a build.

Communication Channels

  • #internal-releases-mobile-apps: Codemagic build status and failures, nightly e2e results
  • #releases-7mind-flutter: human-readable release messages
  • #translations-requests: translations of the store release notes
  • #activation-team-public: questions about SKUs and pricing surfaces

Manual Steps That Still Hurt

The process is largely automated but several steps remain manual: running release-drafter, starting the Codemagic builds, ensuring what's new translations are ready, publishing the Android draft, submitting for review, walking the Android rollout up. These are flagged in the Notion source pages as candidates for further automation.