pipenv install --deploy now fails after having worked for months

Issue

pipenv install --deploy now fails in my docker build step due to out of date lockfile.

However whenever I run pipenv lock, it fails to update the hash and instead spits out the original hash that it already was.

Expected

I expect the dependencies to install, as they have been for almost 6 months with no issue.

Actual result

✔ Successfully created virtual environment! 
Virtualenv location: /root/.local/share/virtualenvs/-x-v5uFv0
Your Pipfile.lock (ab547e) is out of date. Expected: (9d352e).
Usage: pipenv install [OPTIONS] [PACKAGES]...

ERROR:: Aborting deploy

Steps to replicate

• RUN pipenv install --deploy (in a Docker build step, having copied in the Pipfile and Pipfile.lock)

---

output.txt

[matteius]

Sorry for those issues folks – pipenv==2022.10.10 has been released which includes the fix for the Pipfile hash changing, and also the fix for the metadata writing to the lock file at the end of the lock phase.

@Nick-Yazdani the hash generation changed back to how it was before – you may need to re-lock again to get back to that point.

[matteius]

@Nick-Yazdani I opened a PR that I think addresses the issue – the fix is to always re-write the meta section of the generated lockfile dictionary, prior to writing it to the file. I am not sure how it ever worked in the prior implementation, but I don’t imagine this causing many other issues (though one test is failing with this change). Will run through test suite and think through it some more, if possible will cut a new release tomorrow.