release-management

Prevent broken Flutter releases by enforcing a local build-and-test verification gate that runs flutter analyze and flutter test, builds the release APK, and requires explicit user validation before any git commit, tag, or push triggers CI/CD.

The safest way to coordinate git tags with pubspec version updates is a consent-first workflow that standardizes changelog updates and pubspec version bumping, then gates the git lifecycle behind explicit user permission before pushing release tags.

Verify a release APK by building it locally after running flutter analyze and flutter test, then manually validating the artifact's stability and behavior before granting permission to finalize the git commit and push the release tag.

Yes, you can require manual approval by using a consent-first workflow that applies permission-gated git actions, ensuring explicit real-time user confirmation is given before committing changes, tagging a version, or pushing triggers for GitHub releases.

Resolve tag conflicts or ProGuard issues during a Flutter release by following built-in troubleshooting guidance that addresses common release pitfalls, including tag conflicts, ProGuard configuration, and backup completeness for settings migrations.