That's odd indeed. My suspicion is that turbo can't detect the package manager version. I just read through some of the turbo source code and it relies on packageManager field in package.json to detect the version. Do you have yarn@x.x.x listed in your package.json as packageManager?