-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
poetry update --dry-run
modifies poetry.lock
#3766
Comments
This is highly annoying in case of merge conflicts in the lock file. Using |
Does this also affect |
Yes, I would think so, because in addition to the |
Bug still present in the latest |
Still present in 1.2.0b1. Please proceed with PR. Much appreciated. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
-vvv
option).Issue
When
poetry update
is called with the--dry-run
argument, the expected outcome is that the filepoetry.lock
remains unmodified.However, a regression introduced in poetry version 1.1.1 (it seems, via PR #3034) modifies this file regardless of the
--dry-run
flag.To reproduce using the above gist:
With poetry 1.1.0, it works as expected:
As of now, poetry's
master
is also affected. It happens regardless of theexperimental.new-installer
andinstaller.parallel
settings.I have already written a unit test to reproduce this and an according fix that I'll submit as a PR in a minute.
The text was updated successfully, but these errors were encountered: