Menu
Procedure for upgrading the Flutter and Dart SDK versions across the monorepo. Covers FVM config, GitHub actions, pubspec.yaml constraints, and changelogs.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Classify, audit, and author files in docs/ against the Diátaxis framework (tutorial / how-to / reference / explanation). Use when adding, restructuring, or reviewing a docs/*.md file — keeps each doc to one quadrant. Excludes design, spec, plan, and archive documents.
Riverpod 3 Notifier patterns, go_router routing, SharedPreferences persistence, and Flutter UI conventions for fs-game-score. Use for any feature work or provider change, splash/score-table flows, adding or translating user-facing strings (.arb files, gen-l10n), localizing semantic labels, and Mille Bornes / game-mode terminology — even when the request doesn't mention architecture or l10n by name.
LAN host/spectator live score sync for this app: WebSocket wire protocol, mDNS discovery, QR-code join, PIN and app-version validation, and the host/join/ spectator UI. Use when changing gameSyncHostProvider, gameSyncSpectatorProvider, the join or live-share screens, the connection banner, or anything mentioning spectators, live sharing, QR scan, or ws:// URLs.
Version tagging, pubspec/CHANGELOG bumps, distributable builds, and store release notes for fs-game-score. Use when cutting a release, running tag-push.sh, or preparing CHANGELOG sections.
Unit, widget, and integration testing patterns for this app: ProviderScope overrides, integration_test helpers (launchApp, waitForScoreTable, pumpUntilFound), fake sync transports, widget-key lookups in tests, and accessibility/semantics checks. Use whenever writing, fixing, or reviewing any test, debugging a flaky integration flow or splash-clear race, or changing screen-reader/a11y behavior.
Widget keys, semantics, and modal layout rules for player/round UI in this app. Use when editing score table cells, modals, splash configuration, or form fields.
| name | fs-game-score-release-flutter-upgrade-sdk |
| description | Procedure for upgrading the Flutter and Dart SDK versions across the monorepo. Covers FVM config, GitHub actions, pubspec.yaml constraints, and changelogs. |
Follow this procedure when upgrading the Flutter and Dart SDK versions used in this repository. Ensuring all configurations, packages, and CI pipelines stay in sync is critical for monorepo health.
Related skills: fs-game-score-release-engineer
(SKILL.md) — version tagging,
CHANGELOG bumps, and distributable builds once the SDK upgrade lands.
FVM is the source of truth for the local development environment. fvm flutter --version will automatically update the fvm managed local flutter to the correct version if it is not already installed.
You can manually update flutter versions by running:
fvm install <new-flutter-version> (e.g., fvm install 3.44.0) in the root of the repository if the new target version of flutter is not already installed.fvm use <new-flutter-version> (e.g., fvm use 3.44.0) in the root of the repository..fvmrc — the tracked source of truth — now reads { "flutter": "<new-flutter-version>" }, and commit it. (.fvm/fvm_config.json is a legacy, gitignored file fvm use also writes; .fvmrc is the one that must be committed.)The GitHub Actions workflows must use the exact same Flutter version as FVM to prevent CI drifts.
.github/workflows/ for subosito/flutter-action (this repo uses platform integration workflows, e.g. android_integration_test.yaml, ios_integration_test.yaml, macos_integration_test.yaml, windows_integration_test.yaml).flutter-version: parameter to match the new FVM version exactly.pubspec.yaml FilesAll packages in the monorepo should share the same minimum Dart/Flutter SDK requirements.
Locate all pubspec.yaml files across the repository.
Update the environment: constraints to match the new minimum Dart SDK (and optionally Flutter SDK) corresponding to the new Flutter version.
environment:
sdk: ^<new-dart-version>
Document the SDK bump so consumers of the packages are aware of the new minimum requirements.
CHANGELOG.md file for every updated package under the Unreleased or upcoming version heading.- Require Dart SDK <new-dart-version> and Flutter <new-flutter-version>Some skills pin the Flutter version in prose (e.g. run-fs-game-score states the
.fvmrc-pinned version so agents don't corrupt the build cache with a mismatched
system Flutter). Stale mentions silently mislead future sessions.
.claude/skills/ (canonical location; .agents/skills is a symlink to it)
for the old Flutter version and update every hit to the new version.AGENTS.md and README.md if they name the version.Ensure that the new SDK version does not break existing code or cause new linting errors.
fvm flutter pub get or upgrade at the workspace root).fvm flutter analyze to catch any new static analysis errors or deprecations introduced by the newer SDK.fvm flutter test to ensure all tests continue to pass.