dart-resolve-package-conflicts

Open pubspec.lock, locate the YAML block for the conflicting package, and delete only that entry. Then run dart pub get to resolve a compatible version, and verify with dart pub deps. Never delete the entire lockfile, as that causes uncontrolled upgrades.

Run dart pub outdated to see Upgradable and Resolvable columns. Use dart pub upgrade for versions allowed by current constraints, or dart pub upgrade --tighten to update lower bounds in pubspec.yaml. For major versions, manually edit the constraint first.

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

No, deleting the entire pubspec.lock causes uncontrolled upgrades across the whole dependency graph. Instead, remove only the specific conflicting or retracted package's entry and run dart pub get to re-resolve just that package.

Delete the retracted package's block from pubspec.lock and run dart pub get to fetch the newest compatible non-retracted version. If resolution still fails, identify the transitive dependency causing the lock and update its constraint in pubspec.yaml.

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