dart-flutter-sdk-upgrade

Updates Dart and Flutter SDK constraints in pubspec.yaml and CI workflows.

162|23|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/VeryGoodOpenSource/vgv-ai-flutter-plugin --skill dart-flutter-sdk-upgrade-verygoodopensource
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dart-flutter-sdk-upgrade
Source: https://github.com/VeryGoodOpenSource/vgv-ai-flutter-plugin/tree/main/skills/dart-flutter-sdk-upgrade
Command: npx skills add https://github.com/VeryGoodOpenSource/vgv-ai-flutter-plugin --skill dart-flutter-sdk-upgrade-verygoodopensource

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Bumping a Flutter or Dart SDK version touches pubspec.yaml environment constraints and CI workflow version pins, and the Flutter-to-Dart version mapping is easy to get wrong, producing version-solving failures and mixed-scope PRs. ## Core Features & Use Cases - Version Resolution: Looks up the Dart version bundled with a target Flutter release from the official archive instead of guessing from memory. - Constraint Updates: Applies the correct pinning format for each file — MAJOR.MINOR.x for Flutter CI, exact patch for Dart CI, and caret-pinned patch in pubspec.yaml. - Conflict Reporting: Diagnoses pub get version-solving failures, identifies blocking direct or transitive dependencies, and reports them without silently resolving. - Use Case: When asked to bump a repository to Flutter 3.41, the Skill updates the flutter_version in the reusable workflow, sets the matching Dart sdk: constraint in every package's pubspec, verifies with pub get and analyze, and keeps dependency bumps out of the PR. ## Quick Start Ask the assistant to bump Flutter to a target version in this repository and update the SDK constraints and CI workflow accordingly.

Frequently Asked Questions about dart-flutter-sdk-upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bump the Flutter SDK version in a Dart or Flutter package?

Update the `flutter_version` in the CI workflow using MAJOR.MINOR.x format and set the `sdk` and `flutter` constraints in pubspec.yaml. Verify with `flutter pub get` and `flutter analyze` before committing.

How do I find which Dart version ships with a Flutter release?

Check the Flutter release archive at docs.flutter.dev/install/archive, which lists the bundled Dart version beside each Flutter stable release. The Dart number cannot be derived from the Flutter number and should never be stated from memory.

What is the difference between Flutter and Dart CI version pinning?

Flutter CI workflows use MAJOR.MINOR.x format so CI resolves to the latest patch automatically, while pure Dart workflows pin the exact patch version via the `dart_sdk` key. Pubspec constraints use caret syntax with a specific patch version.

Why does pub get fail after updating the SDK constraint?

A dependency likely caps the Dart SDK below the new target, causing version solving to fail. Read the solver output bottom-up to find the blocking package and its constraint, then report it — raising that dependency belongs in a separate PR.

Can I bump dependencies in the same PR as the SDK upgrade?

No. SDK upgrade PRs should contain only CI workflow and pubspec.yaml environment changes. Mixing dependency bumps makes the diff impossible to bisect when something breaks, so dependency updates ship as their own PRs.