Skip to content
Discussion options

You must be logged in to vote

There is not a way to do so. The lock file is not intended to maintain a strict locking of dependencies -- instead it is meant to provide reproducibility. The idea is that your project is checked in CI, and the lock file is bumped often as devs go about their work. CI and your test suite verifies that the latest versions are good and that lock ensures that your production deploy matches CI. If you want to conservatively update versions, you should constrain things properly in your pyproject.toml.

TL;DR: no, the lock file is not a substitute for proper constraints.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@commentator8
Comment options

Answer selected by neersighted
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants