Framework semantic default
Poetry lock no longer updates dependencies by default poetry 2.0 lock --regenerate --no-update
A dependency bump script runs successfully but the lockfile retains old versions.
Agent Quick Fix
Repair against the current Poetry contract, then keep the change narrow and source-backed.
Product: Poetry
Current-contract area: poetry lock no longer updates dependencies by default
Likely root cause: A dependency bump script runs successfully but the lockfile retains old versions.
Repair direction: Verifier checks behavior across multiple requests/build modes, not merely compilation. Check reproducibility from a clean environment and artifact contents where relevant.Symptom
A dependency bump script runs successfully but the lockfile retains old versions.
Why This Happens
Local code often type-checks under both old and new framework semantics; the failure depends on the installed framework version and current runtime defaults.
Common Wrong Fixes
- Changing local code without checking the current external contract.
- Retrying the same install, build, or API call with no version/source change.
- Applying a broad unsafe bypass when a narrow compatibility fix is available.
Codex Search Keywords
These are the search terms observed in a neutral Codex validation run for this failure shape.
Poetry lock no longer updates dependencies by default poetry 2.0 lock --regenerate --no-update
site:python-poetry.org poetry lock update dependencies by default --no-update
python-poetry.org docs cli lock regenerate Poetry lock command
https://python-poetry.org/docs/cli/
'## lock' in https://python-poetry.org/docs/cli/
https://python-poetry.org/docs/1.8/cli/
'## lock' in https://python-poetry.org/docs/1.8/cli/