This is how the chefdk-windows.rb project file looks like right now: 
```
dependency "preparation"
dependency "ruby-windows"
dependency "libyaml-windows"
dependency "ruby-windows-devkit"
dependency "chef-windows"
dependency "chefdk"
dependency "chef-client-msi"
```
where `chefdk` project pulls in many things.

We can change this optimize for the current logic here. But to me it's somewhat counter-intuitive why a dependency change of `chefdk` would trigger build of something before it. Maybe this is the optimum for server pipelines don't know.