Learn

Release Candidate Flow

Treat release as a pipeline with evidence, not a final command.

Flow

  1. Freeze target matrix.
  2. Run static gates.
  3. Run unit/widget tests.
  4. Run integration or manual smoke on target devices.
  5. Build profile mode for performance checks.
  6. Build release artifact.
  7. Install or serve the release artifact.
  8. Check accessibility and local data flows.
  9. Prepare store metadata, privacy declarations, screenshots, and signing.
  10. Release to internal/test track first.

Evidence Log

Target: Android
Flutter version: <version>
Commit: <sha>
Commands: flutter analyze; flutter test; flutter build appbundle --release
Device smoke: Pixel 7 emulator API 35
Manual checks: export, restore, TalkBack basic flow
Blocked: iOS, no Apple signing on this machine

Stop Conditions

  • Signing secret is missing or unclear.
  • Store policy-sensitive permission is not justified.
  • Local data migration or restore fails.
  • Accessibility blocks core flow.
  • Performance was measured only in debug mode.