Private packages not updated unless environment is removed #5791
Description
Issue description
Private packages defined with an object like mylib = {ref = "dev" git = "ssh://git.mycompany.com/my-lib.git"} are not being updated on my virtual env, even after the pipenv update creates a new Pipfile.lock with the correct commit id.
Expected result
After calling pipenv update, I expect the Pipfile.lock ref to change and also the code in my environment to change, such that I have access to the new code within my project.
Actual result
I see the Pipfile.lock ref change, but the actual code for my dependency does not change.
If I do pipenv --rm to remove the environment and then re-create the environment, I can get the actual code change to replicate on disk.
Steps to replicate
Update my-lib with some code change, commit and push. On my project, do pipenv update and wait for the process to finish.
Check that the Pipfile.lock has changed and has the correct ref for the new commit in my-lib.
Check that the code for my-lib hasnt actually changed within my original projects virtual env.