I ran into this earlier where installing a vcs from CLI yields the wrong Pipfile entry such that it cannot lock; I iterated on this bug here -- I believe there are reports of this in the backlog as well.
Fixes #6218
The checklist
[X] Associated issue
[X] A news fragment in the news/ directory to describe this fix with the extension .bugfix.rst, .feature.rst, .behavior.rst, .doc.rst. .vendor.rst. or .trivial.rst (this will appear in the release changelog). Use semantic line breaks and name the file after the issue number or the PR #.
I ran into this earlier where installing a vcs from CLI yields the wrong Pipfile entry such that it cannot lock; I iterated on this bug here -- I believe there are reports of this in the backlog as well.
Fixes #6218
The checklist
news/directory to describe this fix with the extension.bugfix.rst,.feature.rst,.behavior.rst,.doc.rst..vendor.rst. or.trivial.rst(this will appear in the release changelog). Use semantic line breaks and name the file after the issue number or the PR #.