Summary

I am trying to figure out why the --affected flag doesn't seem to be working for me, and in the process of going down this rabbit hole I have come across the dependencies and dependents output that is a part of --dry-run runs of turbo.

The screenshot below is for a library that should both depend on several others in my repo - both dependencies and devDependencies - and be depended on by an application in my library. The command being run is turbo test --affected --dry-run.

I have two questions:

• What are the dependencies and dependents in the screenshot below supposed to reflect? Do they have anything to do with how --affected is supposed to work?
• Why is --affected always resulting in all of my packages running their task, instead of only running the packages that have changed or have a dependency that has changed?

Additional information

• I am using pnpm and my pnpm workspace file has been sufficient for all other tools that rely on it
• I have also tried duplicating my workspace configuration into my root package.json. I see no difference in behavior with or without this change.
• I have set turbo to latest in my package.json and am using pnpm@9.15.2, which is latest at time of writing
• My dependencies inside the monorepo are expressed using the pnpm convention of "workspace:*", e.g. "@oneapp/oneapp-example-feature": "workspace:*"

Example

I am working in a private repo so I cannot link to it. I could try to create a minimum reproducible example but I wouldn't even know what parts of the project would be relevant to causing this issue.