`--sync-workspace-lock` not working with `lerna version`

Describe the bug

I’m not sure if this is design behavior, --sync-workspace-lock maybe only is only meaningful for lerna release, but I don’t have a new version to release yet so I can’t try with lerna release. 🤣

Expectation

Run lerna version --sync-workspace-lock should changes pnpm-lock.yaml.

Reproduction

Clone https://github.com/johnsoncodehk/volar and run and run $ pnpm i && npm run version:test.

Lerna config and logs

lerna.json

{
	"packages": [
		"extensions/*",
		"packages/*"
	],
	"version": "0.37.3"
}

Environment Info

| Executable        | Version |
| ----------------- | ------- |
| `lerna --version` | 4.0.0 |
| `npm --version`   | 8.5.5 |
| `yarn --version`. | 1.22.4 |
| `pnpm --version`  | 7.0.0 |
| `node --version`  | v16.15.0 |

Used Package Manager

pnpm

Validations

• Follow our Code of Conduct
• Read the docs.
• Check that there isn’t already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion.
• The provided reproduction is a minimal reproducible example of the bug.

[johnsoncodehk]

I don’t know it, but I think I will not use workspace: after take a look, because it’s only works for pnpm publish, but the pakcages in https://github.com/johnsoncodehk/volar/tree/master/extensions are is use vsce not pnpm to release. If I only use workspace: for https://github.com/johnsoncodehk/volar/tree/master/packages packages it brings some inconsistencies and confusion to the project. But thanks for let me know it!

Thanks for the kind words, glad to know that my approach was correct and that I wasn’t the only one with that in mind 😃

Please trust your decision more in the repo. 😃

[johnsoncodehk]

I always prefer 1. if I can, because more explicit behavior means less code, less documentation, and more predictability to me. But I believe peoples have different expectations.

Let me know what you think is best, you are my biggest user after all (the lib with the most stars), happy to have you on board 😉

I’m think large projects just can’t move so fast to migrate to lerna-lite in a short period of time, but I would definitely recommend lerna-lite to others. 😉