is there a goal / command we could run in CI to enforce that all of our 3rd-party

python_requirement

constraints are actually resolvable? we’re still using old-style

constraints.lock

for now while we migrate onto the new lockfiles. a PR updated a package version in

constraints.lock

, but not the matching version spec in a

python_requirement

target. our CI is set up to use

--changed-since

heavily, so the error wasn’t caught during PR (because the

python_requirement

hadn’t changed, and none of the downstream files using it had changed). I’d like to add a CI job that does a global sanity-check on our dependencies to avoid errors like this in the future. my first thought was to run

./pants export ::

, but that can take awhile to execute in our codebase… is there any other option that might be quicker to run?