Can nx affected detect upstream dependency changes?

[reoquitous]

Can nx detect when projects are affected by third party library updates? Migrating between nx versions often introduces breaking changes, but they get overlooked in our CI pipeline since we rely on nx affected to detect which tests to run. I understand this may be out of scope, but any common workarounds would be helpful too. It's the kind of thing a developer performing the migration wouldn't know unless it already led to issues before.