Process for upgrading a shared dependency across a specified scope

I’m wondering what the process for updating a shared external dependency across multiple packages should be. This could be my lack of understanding and/or a feature request.

Expected Behavior

Let’s say you have a shared external dependency shared-module which gets updated. You now want to update that dependency across two modules that use it:

$ lerna add shared-module scope=module-1,module-2 # add the latest version of shared-module to module-1 and module-2
$ lerna add shared-module@x.y.z scope=module-1,module-2 # add shared-module@x.y.z to module-1 and module-2

Current Behavior

Lerna detects that shared-module is already a dependency of module-1 (even though it’s an older version) and does nothing:

$ lerna add shared-module@3.10.3 --scope=module-1
lerna info version 2.11.0
lerna info scope my-module
lerna WARN No packages found in scope where shared-module can be added. 

Possible Solution

Perhaps some method akin to npm install and/or npm upgrade that can be applied across selected lerna scopes.

lerna.json

{
  "lerna": "2.11.0",
  "packages": [
    "packages/apps/*",
    "packages/lib/*",
    "packages/services/*",
    "packages/tools/*"
  ],
  "version": "4.0.0"
}

Context

Trying to manage a shared, external dependency (that we can’t pull into the monorepo itself) and maintain consistent dependencies across our entire codebase

Your Environment

Executable	Version
lerna --version	2.11.0
npm --version	6.1.0
node --version	10.3.0

[evocateur]

yeah, lerna add doesn’t do that right now. lerna upgrade is not implemented yet.

[evocateur]

It’s something I’d like to do, and would certainly collaborate actively if someone wants to make a pull request.