Mobile Release Publish Gate

Overview

Apply a release safety gate before publish. If stability evidence is insufficient, return NO-GO and provide a minimal remediation path.

Workflow

1. Snapshot release state

• Run scripts/release_publish_snapshot.sh <repo_root>.
• Capture version markers, CI/release files, notes, and automation lanes.

2. Validate release readiness

• Build/test/lint status.
• Versioning correctness (versionCode, versionName, pubspec version).
• Store listing/release note completeness.
• Crash/blocker risk in critical user flows.

3. Validate publish safety

• Rollout strategy defined (staged rollout recommended).
• Rollback path documented.
• Monitoring plan in place for post-release checks.

4. Decide gate

• NO-GO: unresolved blockers, missing validation, or unclear rollback.