When to use / when NOT to use
- •Use for Flutter SDK upgrades and migration checks.
- •Do not use for dependency-only updates (use
flutter-deps-upgrade).
Preconditions (tools, versions, repo state)
- •Flutter/Dart installed and on PATH.
- •Flutter workspace (
pubspec.yaml) available. - •Clean git state before execute.
Workflow (DISCOVER → PLAN → EXECUTE → VERIFY → REPORT)
- •DISCOVER: inspect Flutter version/channel, monorepo tooling, analyzer config.
- •PLAN: identify upgrade scope and potential breaking-change hotspots.
- •EXECUTE: run
flutter upgradeandflutter pub get. - •VERIFY: run
dart formatcheck,flutter analyze,flutter test. - •REPORT: summarize outcomes and required manual migrations.
Exact commands and expected signals
bash
skills/flutter-upgrade/scripts/run.sh --dry-run skills/flutter-upgrade/scripts/run.sh --execute --ci skills/flutter-upgrade/scripts/run.sh --verify-only --ci
Success: verification pipeline runs and report generated. Failure: missing Flutter toolchain/project or analyzer/test errors.
If it fails (checklist)
- •Run
flutter doctorand resolve toolchain issues. - •Ensure SDK constraints in
pubspec.yamlfit target channel. - •Re-run with
--verboseand inspect first failing stage.
Final report template
- •Current vs upgraded Flutter version/channel.
- •Files affected and dependency lock changes.
- •Analyze/test/build outcomes.
- •Breaking-change follow-ups.
- •Rollback command.