flutter_upgrade_manager 0.1.0

Production-grade Flutter project upgrade and migration management CLI and compatibility engine.

Changelog

All notable changes to flutter_upgrade_manager will be documented in this file.

0.2.0

Compatibility Intelligence

• Added fum why <component> — explains the full chain of compatibility constraints requiring any component (Dart, Gradle, Java, AGP, etc.)
• Added fum conflicts [--json] [--ci] — detects and displays all compatibility conflicts across toolchains and packages.
• Added CompatibilityGraph engine with nodes, edges, explainWhy(), and detectAllConflicts().

Migration Intelligence

• Added fum plan --strategy direct|incremental|conservative|aggressive — multi-strategy upgrade path planning.
• Added MigrationPathPlanner with incremental milestone stepping for large version jumps.
• Added fum explain — explains the rationale and compatibility requirements behind all planned file modifications.
• Added fum upgrade --sandbox — sandbox mode executing upgrades in a temporary isolated copy, leaving the original project completely untouched.

Dependency Analysis

• Added fum dependencies [graph|outdated|conflicts] — comprehensive dependency inspection.
• Added fum dependency-tree <package> — ASCII dependency tree rendering.

Safety & Transaction Engine

• Added MigrationTransaction and TransactionManager with persistent state tracking (prepared, planned, applying, validated, completed, failed, rolledBack).
• Added fum history and fum history show <id> — list and inspect past migration transactions.
• Added fum backup verify — SHA-256 cryptographic integrity verification of backup snapshots.

Validation & Automatic Repair

• Added FailureClassifier — classifies build failures into 12 categories with cause, evidence, affected file, suggested action, and confidence.
• Added fum validate --level basic|standard|full — step-by-step diagnostic failure classification.
• Added fum repair [--dry-run] [--yes] — automatic repair of Kotlin JVM target mismatches, insecure Gradle wrapper URLs, outdated iOS Podfile deployment targets.

Developer & Enterprise Governance

• Added fum health — multidimensional category-level project readiness audit.
• Added fum policy check [--ci] — enterprise policy engine verifying dependency update policies, prohibited licenses, and security constraints.
• Added fum security — vulnerability and discontinued dependency auditing.
• Added fum licenses — license compliance auditing against prohibited license rules.
• Added fum cache [status|clear|update] — local metadata and compatibility rule cache management.

Architecture

• Added FumEventBus with 10 lifecycle events for CLI, CI, and IDE integration.
• Added DiffReporter with semantic diffs including reasons and affected file explanations.
• Enhanced FumConfig with EnterprisePolicy, dependencyUpdatePolicy, and copyWith.
• Registered all 21 CLI commands and subcommands in FumCommandRunner.

Testing

• Expanded test suite from 37 to 85 tests covering all new engines and commands.

0.1.0

• Initial release of Flutter Upgrade Manager (fum) CLI and compatibility engine.
• Implemented fum doctor for deep environment & toolchain inspection (Dart, Flutter, FVM, Git, Java, Gradle, Android SDK, Xcode, CocoaPods, Ruby).
• Implemented fum status for project analysis (Flutter, Dart, FVM, dependencies, Android Groovy/KTS, iOS Podfile/Xcode, Git status, monorepos, flavors).
• Implemented fum plan with verified multi-dimensional compatibility engine (Flutter SDK, Dart SDK, pub.dev packages, Gradle, AGP, Kotlin, Java, compileSdk/targetSdk, iOS deployment target, CocoaPods, Xcode).
• Implemented fum sync and fum upgrade with automated git safety checks, timestamped backups (.fum/backups/), non-destructive modifications, and rollback manifests.
• Implemented fum diff for side-by-side OLD → NEW changes reporting.
• Implemented fum validate with post-upgrade health checks (pub get, analyze, test, gradlew tasks).
• Implemented fum backup and fum rollback (--latest or --id <id>).
• Added support for .fum.yaml configuration and policy enforcement.
• Support for --json machine-readable output across all major commands for CI/CD integration.