- OS version and name: Windows 10 (21H2)
- Poetry version: 1.2.0
- Link of a Gist with the contents of your pyproject.toml file:
Issue
Using Poetry 1.1.14 and lock file poetry_1.1.14.lock:
❯ poetry lock --no-update
Resolving dependencies...
The lock file remains unchanged. Then upgrade Poetry up to 1.2.0.
Using Poetry 1.2.0 and lock file poetry_1.1.14.lock:
❯ poetry lock --check
poetry.lock is consistent with pyproject.toml.
❯ poetry lock --no-update
Resolving dependencies...
Writing lock file
It produces a new lock file poetry_1.2.0.lock.
As you can see some versions of the dependencies have been updated.
That is, the changes were not only cosmetic.
I'd also like to note:
- if you don't use a custom source (just remove source block from
pyproject.toml and repeat repro steps), everything works as it should;
- command for checking lock file returned a positive result. So there must be a bug somewhere, either in the check or in the locking.
-vvvoption).Issue
Using Poetry 1.1.14 and lock file
poetry_1.1.14.lock:The lock file remains unchanged. Then upgrade Poetry up to 1.2.0.
Using Poetry 1.2.0 and lock file
poetry_1.1.14.lock:It produces a new lock file
poetry_1.2.0.lock.As you can see some versions of the dependencies have been updated.
That is, the changes were not only cosmetic.
I'd also like to note:
pyproject.tomland repeat repro steps), everything works as it should;