breaking change: invert `lock --no-update` to `lock --update` (or similar)

• I have searched the issues of this repo and believe that this is not a duplicate.
• I have searched the documentation and believe that my question is not covered.

Feature Request

Now that https://github.com/python-poetry/poetry/issues/1614 is fixed and released (yay!), I’d like to propose that for v2, there is a breaking change to make Poetry more opinionated and preserve the versions in the lockfile by default, only updating when explicitly asked to (such as with the update command or some kind of --update flag to lock). Doing so follows the patterns in analogous tools like Yarn and Cargo and adheres to the principle of least surprise.

See also the philosophically-related https://github.com/python-poetry/poetry/issues/2370.

[michalszelagsonos]

+1 for this feature. Our project is pretty big where many folks, with various skills, contribute and when dependencies move in unexpected ways, it creates lots of waves. It’s better to be explicit in such situations and do exactly what the user is requesting.

[AleCandido]

Actually, what would be the difference between:

• poetry lock --update: generate the lock file, updating the dependencies
• poetry update: update the dependencies, generating the lock file

No one of the two will change the content of pyproject.toml, and then they both generate a lock file compliant with it.

To me, the two commands are doing the same operation, but maybe I’m just not able to spot the difference.

If this is actually true, it would be confusing to have two different commands performing the exact same operation, so I’d rather propose to make poetry lock always behaving in the --no-update mode, and nothing else. To update, there is a dedicated command.