Do not increment version if a devDep + peerDep?

Say we have packages foo, bar, and baz, with bar and baz having foo as a peer dependency. Both of these packages also have a dev dependency for foo so that npm/yarn install/symlink everything correctly.

Now, when foo is updated and I run lerna publish, it increments the foo dev dependency in bar and baz (even when they haven't been modified), which causes a patch version to be published for these 2 packages. These patch versions are completely unnecessary.

It would be nice to avoid this if possible, possibly through a CLI flag.

Expected Behavior

N/A, not sure it's scoped.

Current Behavior

It unnecessarily releases versions when devDeps are updated.

Possible Solution

Disable through a CLI flag? Don't increment devDep if also a peerDep?

Context

This is causing unnecessary patch releases for packages.

Your Environment

Start with the lerna publish flow and the dependency/versioning logic that updates foo in bar and baz; reproduce the case where foo is both a devDependency and peerDependency. Determine the intended scope for a flag or dependency rule, then verify that unchanged packages no longer receive unnecessary patch releases.