`poetry update` with git-based dependencies updates `poetry.lock` but not the virtual environment

• I am on the latest beta Poetry version.
• I have searched the issues of this repo and believe that this is not a duplicate.
• If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

• OS version and name: MacOS Catalina 10.15.6
• Poetry version: 1.1.0b2
• Link of a Gist with the contents of your pyproject.toml file: https://gist.github.com/jeffcasavant/7454acfce0933e2f4758a35699e890aa

Issue

I have a git dependency that is defined with a branch instead of a specific commit or revision. As a result, the commit that the reference points to can change.

poetry update successfully updates the poetry.lock file with the correct latest commit, but the library in the virtual environment remains checked-out at the commit that was latest when poetry install was last run.

Replication

• Add a git-based dependency to a poetry project.
• poetry install
• Note the commit hash that was installed (e.g. inside poetry shell, cd $VIRTUAL_ENV/src/<git dependency name> && git log | head -1)
• Note the commit hash that was set in poetry.lock (cat poetry.lock | grep -i <git dependency name> -B 2 | grep -i reference worked for me, but obviously YMMV; you’re looking for the reference field in the package.source block with the url equal to the git repository you installed from)
• Push another commit to the git-based dependency.
• poetry update <git dependency name>
• Note that the reference in poetry.lock has changed
• Note that the checked-out commit in src has not changed

I expected that since poetry.lock was updated that my virtualenv was updated as well.

[thehappydinoa]

Hi, I am still dealing with the same issue. Is there anything we can do to have this escalated/reopened? Maybe @sdispater or @abn ?

[revolter]

The workaround that I used was to comment out the package line in the pyproject.toml file, run poetry install, then uncomment it back and run poetry install again.