Problem
fvm 4.0.5 depends on pub_updater: ^0.4.0. Other common dev tools (e.g., melos) have moved to pub_updater: ^0.5.0. Since these constraints are incompatible, fvm can't coexist as a dev_dependency in projects that also depend on packages requiring pub_updater ^0.5.0.
This is especially problematic with Dart pub workspaces (Dart 3.6+), where all packages in a monorepo share a single dependency resolution.
Proposed fix
Bump pub_updater from ^0.4.0 to ^0.5.0 in fvm's pubspec.yaml. The 0.5.0 release contains no breaking API changes — it was a "tighten dependencies" maintenance release.
Problem
fvm 4.0.5 depends on
pub_updater: ^0.4.0. Other common dev tools (e.g., melos) have moved topub_updater: ^0.5.0. Since these constraints are incompatible, fvm can't coexist as a dev_dependency in projects that also depend on packages requiringpub_updater ^0.5.0.This is especially problematic with Dart pub workspaces (Dart 3.6+), where all packages in a monorepo share a single dependency resolution.
Proposed fix
Bump
pub_updaterfrom^0.4.0to^0.5.0in fvm'spubspec.yaml. The 0.5.0 release contains no breaking API changes — it was a "tighten dependencies" maintenance release.