dart-resolve-package-conflicts

Open pubspec.lock, delete only the YAML block for the conflicting package, then run dart pub get to re-resolve that package. Never delete the entire lockfile, since that triggers uncontrolled upgrades across the whole dependency graph.

Run dart pub outdated to see Upgradable and Resolvable columns. Use dart pub upgrade for constraint-allowed updates, dart pub upgrade --tighten to bump lower bounds automatically, or manually edit pubspec.yaml constraints for major version jumps.

Current is the version in pubspec.lock, Upgradable is the latest allowed by your pubspec.yaml constraints, Resolvable is the latest achievable given all dependencies, and Latest is the newest published version excluding prereleases.

Deleting the whole lockfile forces pub to re-resolve every dependency, causing uncontrolled upgrades across the graph. Removing only the conflicting package's entry keeps all other versions pinned while fixing the specific conflict.

Locate the retracted package's block in pubspec.lock and delete only that entry, then run dart pub get to fetch the newest compatible non-retracted version. Verify the result with dart pub deps to confirm the graph resolves correctly.

Use dart pub get --enforce-lockfile in CI/CD pipelines so the exact versions recorded in pubspec.lock are installed. This guarantees production builds match the dependency versions tested locally.