Comment on #17325 Why is an un-inferred dependency a warning, rather than an error, and should it stay that way? Discussion answered by benjyw I'm not convinced it is an error in every case - you could, for example, be importing from a package that you know is available at runtime. Making this an error would probably require support for dependency scopes, so we can express the idea of a "provided" dependency. But allowing repos to opt-in (or out, eventually) of this being an error sounds like a good idea. All that said, I'm not sure I see the correctness issue? If you had a typo, for example, then when you fix the typo that file is invalidated. pantsbuild/pants