[BUG] `npm version` with workspace will not write new data back to `package-lock.json`

[zthxxx]

Is there an existing issue for this?

• I have searched the existing issues

This issue exists in the latest npm version

• I am using the latest npm

Current Behavior

1. run npm version for workspaces with -w <workspace> args
2. see only changed package.json but not change lockfile

Expected Behavior

run npm version -w <workspace> need adjust new version of workspace package in package-lock.json

As it said in npm cli docs:

Run this(npm version) in a package directory to bump the version and write the new data back to package.json, package-lock.json, and, if present, npm-shrinkwrap.json.

Steps To Reproduce

1. run npm version for workspaces with -w <workspace> args
2. see only changed package.json but not change lockfile
3. for verify whether lockfile need update, I have run npm install
4. yes, lockfile changed

Environment

• npm: 8.3.0
• Node: 16.8.0
• OS: macOS 11.15
• platform: Mac
• npm config:

audit = false
fund = false
if-present = true
ignore-scripts = false
yes = true

[wraithgar]

Closing as a duplicate of #3403

[zthxxx]

My solution: move to using pnpm

[jonthomp]

@wraithgar @fritzy please can this be re-opened? I don't think it is a duplicate of #3403.

The bug here is that running npm version -w=<workspace> does not update package-lock.json

[wraithgar]

~/D/n/s/ws (main|✔) $ npm version minor -w workspace-a
workspace-a
v1.1.0

added 2 packages in 469ms
~/D/n/s/ws (main|✚2) $ git diff package-lock.json 
diff --git a/package-lock.json b/package-lock.json
index 119a66b..08a7625 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -32,7 +32,7 @@
       "link": true
     },
     "workspace-a": {
-      "version": "1.0.0",
+      "version": "1.1.0",

It does though?

[jonthomp]

Sorry, I forgot to try it out on the latest npm, it does indeed work. We're currently on 8.5.5 where it does not. We will update. Thanks.