[BUG] npm --workspaces version doesn't update dependencies

[niemyjski]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

The npm --no-git-tag-version --workspaces version <version> command doesn't update package devDependencies or dependencies with the new version. I'd expect that workspace dependencies would be updated to match the new versions that were set.

Expected Behavior

npm --no-git-tag-version --workspaces version "2.0.0-alpha1" should update all workspace package versions (currently does) and also update the package dependency versions

Steps To Reproduce

1. Setup a new npm workspace
2. Create /packages/packagea :

{
  "name": "packagea",
  "version": "2.0.0-dev"
}

3. Create ``/packages/packageb`:

{
  "name": "packageb",
  "version": "2.0.0-dev",
  "dependencies": {
      "packagea": "2.0.0-dev"
    }
}

3. Run npm --no-git-tag-version --workspaces version "2.0.0-alpha1"
4. notice the package versions are updated but the dependencies are not.

I have an existing setup located here: https://github.com/exceptionless/Exceptionless.JavaScript/tree/feature/workspaces that reproduces it (but package names are changed...)

I noticed this after getting the following error:

npm ERR! code ETARGET
npm ERR! notarget No matching version found for @exceptionless/[email protected].
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

Environment

• OS: Windows 10 latest
• Node: v16.1.0
• npm: 7.17.0

[wraithgar]

#4193
#3757

[Roaders]

I came across this issue as well so wrote a script to fix it:
https://www.npmjs.com/package/workspace-version

just add:

version: "workspace-version -g"

to your root package.json scripts to update all child package json versions, update depenendency versions of siblings and add modified files to git (that's the -g) when you do $npm version patch. If you use it any feedback / issues much appreciated.