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.
• GO WITH RISKS: non-critical issues with mitigation.
• GO: validated and release-safe.

5. Publish checklist output

• Include exact blockers, required actions, and release owner handoff notes.

Output Format

Use this structure:

# Release Publish Gate

## Decision
NO-GO | GO WITH RISKS | GO

## Blockers
1. ...

## Risks
1. ...

## Required Before Publish
1. ...

## Play Store Checklist
- Versioning:
- Release notes:
- Rollout plan:
- Rollback plan:

## Verification Evidence
- Commands/results:
- Confidence:

Guardrails

• Never publish recommendation without fresh verification.
• No dependency/platform bumps inside release freeze unless explicitly approved.
• Default to NO-GO if evidence is incomplete.

Resources

• scripts/release_publish_snapshot.sh
• references/playstore-publish-checklist.md
• references/release-risk-rubric.md