#18181 Adding a command to check the validity/compatibility of a lock-file Issue created by TalAmuyal I'd like to have a command I can run that tells me whether or not the lock-file is synced with the requirements and constraints. To clarify, I'm not asking if packages could be pinned to a newer version in the lock-file. Instead, I'd like to know if that lock-file is still valid. Example: If I have a constraint for

pytest<=1.0.0

and the lock-file has

pytest==1.0.0

, than I consider the lock-file to be valid. However, if I then change the constraint to

pytest>1.0.0

, then the lock-file is no longer valid and needs to be re-generated. While running a relevant target will result in an error, it is not enough as I'm still in the process of integrating Pants into our flow and, unfortunately, the process will take a few more months. In the meantime, people push new commits that might make the lock-file invalid without it being flagged in CI. pantsbuild/pants