Yarn 4 peer dependency warnings

[Methuselah96]

The Yarn 4 blog post mentions:

You will also notice it doesn't print as much warnings around peer dependencies, as we now try to only print warnings for actionable situations

Where can I read more about this (e.g., what is considered actionable vs. not actionable?)? Is there a way to restore the old behavior (as someone who likes to be aware of and contribute fixes to packages that have peer dependency issues)?

[forcemagic]

Hi!

I believe this is the PR that introduces this change: #5509

About peerDeps, it mentions:

Only peer dependency warnings caused by workspaces are now reporter.
They have also been moved inside the post-resolution validation step.
The resolution step is now expected to only do one of two things: either
report an error when the resolution fails, or report the packages which
got added / removed from the lockfile.

Hope this helps! 🙂