dart-migration-versioning
Managing Dart Language Versions
Contents
- Core Guidelines
- Configuration & Overrides
- Workflows
- Examples
- Breaking Changes Reference
- Related Skills
Core Guidelines
- Check current language version requirements in
pubspec.yamlbefore initiating any migration or refactoring. - Consult breaking change logs before performing major dependency or SDK upgrades.
- Use
@dart = <version>to pin specific files to older versions during gradual migrations (e.g., migrating a large project to a new language feature like sound null safety). - Understand Version Derivation: The default language version for a package is strictly determined by the lower bound of the SDK constraint in
pubspec.yaml. Patch versions do not introduce new language features.
Configuration & Overrides
Global Package Versioning
More from dart-lang/skills
dart-add-unit-test
Write and organize unit tests for functions, methods, and classes using `package:test`. Use when creating new logic or fixing bugs to ensure code remains correct and regression-free.
2.0Kdart-fix-runtime-errors
Uses get_runtime_errors and lsp to fetch an active stack trace, locate the failing line, apply a fix, and verify resolution via hot_reload.
2.0Kdart-run-static-analysis
Execute `dart analyze` to identify warnings and errors, and use `dart fix --apply` to automatically resolve mechanical lint issues. Use during development to ensure code quality and before committing changes.
2.0Kdart-use-pattern-matching
Use switch expressions and pattern matching where appropriate
2.0Kdart-resolve-package-conflicts
Workflow for fixing package version conflicts. Use this when `pub get` fails due to incompatible package versions.
2.0Kdart-collect-coverage
Collect coverage using the coverage packge and create an LCOV report
2.0K