Summary: 7Mind mobile builds are split: Codemagic owns all production iOS and Android builds, while GitHub Actions handles CI (test, lint, codegen, docs), the release tag and the nightly e2e trigger. This is the opposite of the rest of the 7Mind system, which uses GitHub Actions heavily. Sources: direct code inspection of codemagic.yaml and .github/workflows/ in 7mind-mobile-apps-monorepo; re-checked against origin/main at 4.0.9 on 2026-11-09 (codemagic.yaml, .github/workflows/, .github/release-drafter.yml, documentation/docs/sevenmind/deployment.md, PRs 1439 and 1462) Last updated: 2026-11-09


Why it is split this way

iOS and Android builds need platform-specific runners (macOS for iOS, signed-key access for Android), TestFlight + Play Store credentials, and integration with mobile-specific services like Firebase Test Lab. Codemagic specializes in this stack. GitHub Actions on the 7mind-mobile-apps-monorepo runs the things that do not need shipping signed binaries: tests, analysis, code generation verification, translations, codecov, the release tag and the MkDocs publish.

If an agent looks at this repo and asks “where do production builds happen?”, the answer is Codemagic, not GitHub Actions. The README badges and Actions workflows can mislead.

Codemagic workflows

Defined in codemagic.yaml: 10 workflows. Eight build the app, and six of those publish:

WorkflowFlavorTargetPublishes to
flutter-ios-simulatorstaginglib/main_staging.dart(preview only, no publish)
flutter-ios-simulator-prodproductionlib/main_production.dart(preview only, no publish)
ios-workflow-stagingstaginglib/main_staging.dartTestFlight (Internal Testers); provisioning profile 7mind-flutter-distr-stg
ios-workflow-productionproductionlib/main_production.dartTestFlight (Internal Testers); provisioning profile 7mind-dach-flutter-distr
ios-workflow-zpp-submissionzpplib/main_staging.dartTestFlight (Internal Testers); provisioning profile 7mind-flutter-distr-stg
android-workflow-stagingstaginglib/main_staging.dartGoogle Play internal track (draft)
android-workflow-productionproductionlib/main_production.dartGoogle Play internal track (draft)
android-workflow-zpp-submissionzpplib/main_staging.dartGoogle Play internal track (draft)

None of the iOS workflows submits to the App Store; that happens by hand in App Store Connect (see mobile-release). The iOS production workflow skips the unit test step; the other publishing workflows run flutter analyze and the unit tests before building.

Two e2e workflows (e2e-tests-android-workflow, e2e-tests-ios-workflow) run the Patrol suite against the staging flavor on Firebase Test Lab. They run FTL synchronously with a 30-minute timeout, so a failing test fails the build; both devices use locale de so the prevention flow is exercised. patrol_cli 4.6.1 is pinned in codemagic.yaml and must stay paired with patrol 4.8.0 in pubspec.yaml.

Build numbers are auto-incremented by Codemagic using the app-store-connect and google-play CLIs (latest build number plus one). Codemagic posts build start, success and failure to Slack #internal-releases-mobile-apps. The iOS workflows also email nikolas@7mind.de, on success only.

No Fastlane is in use. iOS code signing and submission is driven directly by Codemagic’s xcode-project integrations; Android signing uses keystore env vars (CM_KEYSTORE_PATH, CM_KEYSTORE_PASSWORD, etc.).

GitHub Actions workflows

All in .github/workflows/ on 7mind-mobile-apps-monorepo:

  • test.yml — runs make ci_test on PRs and main pushes
  • analyze.yml — make ci_lint on every push
  • internal_builds.yml — builds a debug staging AAB on main as a smoke test; Slack-notifies on failure. Does not publish.
  • codecov.yml — coverage upload
  • verify_code_gen.yml — runs build_runner and fails if the working tree is dirty
  • localize-gen.yml and translations.yml — translation file generation
  • title-validation.yml — PR title lint
  • release_drafter.yml — every push to main refreshes the draft GitHub Release (PR titles grouped by label, config in .github/release-drafter.yml). Started by hand (workflow_dispatch), it publishes the release, which creates the tag vX.Y.Z, then commits “updated: version to X.Y.Z” to pubspec.yaml and pushes it to main. The tag therefore points at the commit before the version bump (open PR 1545 would reverse the order). The separate release_drafter_release.yml was merged into it in August 2026 (PR 1462).
  • nightly_e2e.yml — cron at 03:00 UTC (and manual): starts both Codemagic e2e workflows through the Codemagic API. Needs the CODEMAGIC_API_TOKEN and CODEMAGIC_APP_ID secrets and reports a failed start to the mobile health Slack webhook.
  • publish_documentation.yml — builds MkDocs and uploads to GCS bucket mobile.6mind.de on main pushes. Service account mobile-docs-write@mind-f62c0.iam.gserviceaccount.com. Doc site at https://mobile.6mind.de/site.
  • publish_catalog.yml — publishes the Bliss UI catalog web build: main to mobile.6mind.de/catalog, each PR to mobile.6mind.de/pr-<number>/web with a comment on the PR. The separate publish_catalog_pr.yml was merged into it in July 2026 (PR 1439).
  • supernova.yml — design system sync

Triggers

  • GitHub Actions: PR opened/synced, push to main, the nightly cron of nightly_e2e.yml, and manual workflow_dispatch where relevant.
  • Codemagic: codemagic.yaml defines no triggers. Release builds are started by hand on the main branch after release_drafter.yml has run (repo doc documentation/docs/sevenmind/deployment.md); build from main, not from the tag, because the tag still carries the previous version. The e2e workflows are started only by nightly_e2e.yml; the Codemagic UI must not hold an e2e schedule as well, or the suite runs twice a night.

What agents should know

  • Don’t migrate mobile builds into GitHub Actions without a strong reason. The split is intentional and the credentials live in Codemagic.
  • When changing pubspec.yaml or platform code that affects build output, both the GitHub Actions verify pipelines and the Codemagic build pipelines must pass for a release to ship.
  • The release-drafter workflow bumps pubspec.yaml version on release publish. Do not also bump it manually in the same PR.
  • Patrol e2e is staging-flavor-only (see pubspec.yaml patrol config). The Firebase Test Lab runs are part of the Codemagic e2e workflows, not GitHub Actions.
  • Docs land on mobile.6mind.de automatically when documentation/docs/** changes on main.