poetry.lock does not match pyproject.toml

What it means

pyproject.toml changed, poetry.lock did not.

The error happened while installing dependencies or building the project. The new version was not started, the current one keeps running.

Typical causes

• The install or build command exited with an error
• Out of memory or disk space
• The language or package manager version is not the one the project expects

How to fix it on mevcore

Run «poetry lock» locally, commit poetry.lock and deploy again.

1. 1 Open the app in the mevcore panel: the Problems card on the overview shows this error and the log line it was found in.
2. 2 After the fix, deploy again. If it fails again, the log ends with [mevcore] lines naming the new error code.
3. 3 The "Ask AI" button next to the error prepares a request for ChatGPT or Claude: the error code, the end of the log without secrets and the app settings.

For an AI assistant

The same in English: paste it together with the log into the AI chat.

mevcore error code: install.poetry_lock_outdated
phase: install and build
diagnosis: poetry.lock does not match pyproject.toml
platform hint: pyproject.toml changed, poetry.lock did not. Run «poetry lock» locally, commit poetry.lock and deploy again.
platform docs: https://mevcore.com/llms-full.txt

Related errors

• install.uv_lock_outdated uv.lock does not match pyproject.toml