Guides Flutter/Dart SDK version upgrades across VGV repositories, updating pubspec constraints and CI workflow versions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/vgv-ai-flutter-plugin:dart-flutter-sdk-upgradeWhen to use
Use when upgrading the Flutter or Dart SDK version in any VGV repository. Trigger on phrases like "bump Flutter to 3.x", "update SDK constraints", "upgrade Dart SDK", "update CI Flutter version", "bump SDK version", or "prep the SDK upgrade PR".
sonnetThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
One PR per project. Only CI workflow and `pubspec.yaml` changes — no logic, no dependency
One PR per project. Only CI workflow and pubspec.yaml changes — no logic, no dependency
version bumps, no test changes.
Apply these standards to ALL SDK upgrade work:
MAJOR.MINOR.x — no caret, .x wildcard resolves to latest patchMAJOR.MINOR.PATCH, no caret, no wildcard^MAJOR.MINOR.PATCH with the specific patch versionpub get and analyze — don't silently resolve conflictsFlutter bundles a specific Dart release — their version numbers do not match. For example, Flutter 3.41.0 ships with Dart 3.11.0. You must look up the correct Dart version for the target Flutter release before editing any files.
How to find the Dart version:
If the user has not specified a Flutter version, look up the latest Flutter stable release from that same page. For pure Dart packages (no Flutter dependency), the Dart version is whatever the user specifies or the latest stable — no Flutter mapping needed.
Confirm both resolved versions with the user before editing files.
.github/workflows/VGV packages use VeryGoodOpenSource/very_good_workflows reusable workflows. Leave the
@v1 tag untouched. Flutter packages use MAJOR.MINOR.x — no caret, literal x as the
patch wildcard so CI resolves to the latest patch automatically. Dart packages pin the exact
patch version. When bumping versions, update MAJOR and/or MINOR as appropriate
(e.g., 3.41.x → 3.42.x or 4.0.x):
Flutter package:
uses: VeryGoodOpenSource/very_good_workflows/.github/workflows/flutter_package.yml@v1
with:
flutter_version: "3.41.x" # ← MAJOR.MINOR.x, resolves to latest patch
Pure Dart package — note the key is dart_sdk, not flutter_version. Use the Dart
version, not the Flutter version:
uses: VeryGoodOpenSource/very_good_workflows/.github/workflows/dart_package.yml@v1
with:
dart_sdk: "3.11.0" # ← exact Dart version (not Flutter version)
If a file uses flutter_channel: stable instead of a pinned version,
pin the version — VGV always pins Flutter versions in CI workflows.
pubspec.yaml environment constraintsFormat is ^MAJOR.MINOR.PATCH (caret, exact patch). Unlike CI, pubspec pins a specific
patch version — the one the user specifies or the current stable at the time of the bump.
Flutter package (has flutter: under dependencies):
environment:
sdk: ^3.11.0 # ← Dart version bundled with the target Flutter release
flutter: ^3.41.0 # ← Flutter version
Pure Dart package (no Flutter SDK dependency):
environment:
sdk: ^3.11.0 # ← Dart version only
# no flutter: line
In a monorepo, update each package's pubspec.yaml individually. The shared CI workflow
only needs updating once.
Run from each package directory. Use Dart/Flutter MCP tools if available; otherwise Bash.
flutter pub get # or: dart pub get (for pure Dart packages)
flutter analyze # or: dart analyze
If pub get fails with dependency conflicts, report them — don't silently resolve by
upgrading packages. If analyze surfaces new errors introduced by the SDK bump, report
them rather than fixing them in this PR.
Before committing, confirm the diff contains only:
.github/workflows/*.ymlpubspec.yaml (one or more)git diff HEAD --name-only
Suggested commit/PR message:
chore: bump Flutter to 3.41.0 / Dart to 3.11.0
- Update flutter_version in .github/workflows/ to 3.41.x (CI resolves latest patch)
- Update dart_sdk in .github/workflows/ to 3.11.0 (exact patch)
- Update environment sdk/flutter constraints in pubspec.yaml
No logic or code changes.
npx claudepluginhub verygoodopensource/very-good-claude-code-marketplace --plugin vgv-ai-flutter-pluginUpgrades the very_good_analysis lint package in Dart/Flutter projects: bumps version in pubspec.yaml, runs dart/flutter analyze, and fixes only new lint warnings for a clean PR.
Guides Flutter development for cross-platform iOS, Android, Web apps. Covers non-interactive CLI, project setup, state management, widgets, GoRouter navigation, platform channels, testing, CI/CD.
Provides expert guidance on Flutter 3.27+ and Dart 3.3+ for building/optimizing mobile/web/desktop apps, covering Riverpod/BLoC state, GoRouter navigation, Drift storage, Patrol testing, on-device AI.