Hi everyone I am using

pants --changed-since=main --filter-target-type="docker_image" publish

to publish docker images in my CI on a python mono repo. We have a large

default.lock

dependency file, which contains all 3rd party dependencies required across all docker images. I have observed that whenever any dependency changes in

default.lock

(as a result of version updates), pants would target and publish every docker image in the repository. This happens even if change in version is limited to only 1 dependency, which is not present in transitive dependencies of multiple docker images in this repo. Is this expected behaviour? Any ideas or help is much appreciated

Hi! Yes, this is expected behaviour, as Pants does not currently know which dependencies changed within your requirements or lockfiles. There is some on going work to improve this situation here: https://github.com/pantsbuild/pants/pull/20531