upgrade

name	upgrade
description	Upgrade Flutter and package dependencies in this repository while keeping .fvmrc, pubspec.yaml, code generation, CI, and tests aligned. Use when bumping Flutter, Dart constraints, direct dependencies, or generator toolchains.
allowed-tools	Bash Read Grep Glob Edit Write
model	claude-sonnet-4-6

Flutter Template Upgrade

Use this skill for SDK and dependency upgrades in this repository.

Read First

• AGENTS.md
• docs/PROJECT_GUIDELINES.md
• .fvmrc
• pubspec.yaml
• makefile
• build.yaml
• .github/workflows/

Upgrade Goals

• Keep .fvmrc and pubspec.yaml aligned.
• Let pub resolve compatible versions rather than guessing.
• Regenerate all generated code after package changes.
• Fix API migrations and lint changes introduced by the newer toolchain.
• Verify local commands and CI still reflect the project pin.

Workflow

1. Check current SDK pin in .fvmrc and pubspec.yaml.
2. Confirm the target Flutter version.
3. Update .fvmrc.
4. Activate the new SDK locally — this always needs to happen after changing .fvmrc:

   fvm install
   fvm use <version>
   fvm global <version>
   

   fvm use <version> updates the project SDK, while fvm global <version> keeps plain flutter commands from resolving through an older global SDK.
5. Update .vscode/settings.json — set dart.flutterSdkPath to .fvm/flutter_sdk. Then restart VSCode (or run "Dart: Change Flutter SDK" from the command palette) so the Dart/Flutter extension reloads against the new SDK. Skipping this causes the IDE to keep analyzing with the old version even though the CLI is already on the new one.
6. Update pubspec.yaml environment constraints to match the new SDK floor.
7. Run dependency audit commands such as fvm flutter pub outdated.
8. Use fvm flutter pub upgrade --major-versions when the goal is to move the dependency graph forward broadly.
9. Review any changed direct constraints in pubspec.yaml.
10. Run:
    • fvm flutter pub get
    • make gen
    • fvm flutter analyze
    • fvm flutter test
11. Fix breakages from:
    • package API changes
    • analyzer/lint changes
    • build runner or codegen config warnings
    • generated native plugin files
12. Review GitHub Actions to ensure they still use the pinned project SDK.

Dependency Conflict Workflow

When pub get, pub upgrade, or code generation fails because of version solving:

1. Read the full solver message and identify the smallest incompatible package chain.
2. Run:

   fvm flutter pub outdated
   

3. Prefer changing direct dependencies in pubspec.yaml over editing transitive constraints.
4. Keep versioned pairs aligned, especially:
   • freezed and freezed_annotation
   • json_serializable and json_annotation
   • riverpod_generator, riverpod_annotation, flutter_riverpod, and riverpod_lint
   • auto_route_generator and auto_route
5. If a single direct dependency is blocking resolution, try the narrowest compatible constraint first rather than a broad major-version sweep.
6. After minor/patch upgrades, run fvm flutter pub upgrade --tighten to raise the lower bounds in pubspec.yaml to the versions actually resolved, keeping constraints honest.
7. If pubspec.lock changes after resolution, review whether the churn matches the intended upgrade scope. Do not hand-edit the lockfile, with one exception: when a single package is retracted or stuck in a conflict, delete only that package's block from pubspec.lock and rerun fvm flutter pub get so pub re-resolves just that package. Never delete the whole lockfile to force a clean resolve — that causes uncontrolled upgrades across the entire graph.
8. After dependency resolution succeeds, rerun make gen before judging analyzer errors. Generated code and analyzer failures are often stale until codegen completes.

Static Analysis Fixes During Upgrades

Analyzer and lint changes are expected after SDK or package upgrades. Handle them in this order:

1. Run fvm flutter analyze and group failures by root cause.
2. Use mechanical fixes only when they are clearly safe:

   fvm dart fix --dry-run
   fvm dart fix --apply
   

3. Review the resulting diff carefully. Revert or adjust mechanical changes that weaken template conventions, generated-code boundaries, or readability.
4. Fix remaining analyzer issues by following docs/PROJECT_GUIDELINES.md and nearby code.
5. Run fvm dart format only after source changes settle.

Common SDK Resolution Failure

If pub get or the IDE package update reports an error like:

The current Dart SDK version is 3.11.4.
Because flutter_app requires SDK version >=3.12.0 <4.0.0, version solving failed.
Try using the Flutter SDK version: 3.44.0.

the project has usually been upgraded correctly, but the command runner or IDE is still using an older Flutter SDK from PATH. Resolve it by:

1. Checking the pinned SDK:

   fvm flutter --version
   fvm dart --version
   

2. Updating the global FVM SDK used by plain flutter commands:

   fvm global <version>
   

3. Ensuring VSCode uses the project FVM symlink:

   {
     "dart.flutterSdkPath": ".fvm/flutter_sdk"
   }
   

4. Restarting VSCode, or running "Dart: Restart Analysis Server" and "Dart: Change Flutter SDK".
5. Running fvm flutter pub get again.

Version Pairs To Check Together

• freezed with freezed_annotation
• json_serializable with json_annotation
• riverpod_generator with riverpod_annotation
• auto_route_generator with auto_route

Common Migration Hotspots In This Repo

• flutter gen-l10n flags in makefile
• build.yaml builder names or deprecated sections
• flutter_local_notifications API changes
• stricter lints from upgraded analyzer and netglade_analysis
• generated files under linux/flutter/ and windows/flutter/
• workflow Flutter pinning in .github/workflows/

Completion Criteria

• .fvmrc and pubspec.yaml match
• pubspec.lock updated
• make gen succeeds
• analyze succeeds
• widget tests succeed
• any remaining unresolved latest versions are explained, not ignored silently