| Instead of manually updating dependencies in a `pubspec.yaml` file, use the [`update-packages`](packages/flutter_tools/lib/src/commands/update_packages.dart) CLI tool: |
| |
| ## To update all dependencies: |
| |
| `flutter update-packages --force-upgrade` |
| |
| ## To pin a dependency: |
| |
| Sometimes you need to prevent a dependency from being updated when you run `flutter update-packages --force-upgrade`. |
| |
| In that case, first pin the dependency in [`kManuallyPinnedDependencies`](https://github.com/flutter/flutter/blob/5bd34ef541575eddae6aaa82fc76a59ae7e464c3/packages/flutter_tools/lib/src/update_packages_pins.dart#L17) and include a comment with a link to an issue to unpin the dependency. |
| |
| You can then re-run `flutter update-packages --force-upgrade`. |
| |
| ## To update a single dependency for cherrypicks: |
| |
| Sometimes you need to update a single dependency as a [cherrypick to a release candidate branch](../releases/Flutter-Cherrypick-Process.md). |
| |
| In that case, you can run: |
| |
| `flutter update-packages --cherry-pick-package=[pub package name] --cherry-pick-version='[pub package version]'` |
