Better communicate on changes on Nx workspace that may breaks Nx community plugins

[tinesoft]

Hi awesome Nx team 👋🏾

First of all, thank you guys for the terrific tool. Us devs love it!

Nonetheless, I want to share my tiny frustration regarding the current plugin author experience, in particular around the communication (or lack of) on changes on Nx workspace that may break community plugins.

For example, this recent change](#4610) in Nx workspace starting v11.2.6 and which consisted in removing @angular-devkit/{core,architect,schematics} dependencies (because of the migration towards @nrwl/devkit), caused my nx plugin to fail upon execution, due to the now missing deps, used by my plugin's schematics.

Another breaking change, was the renaming of the fileutils.ts in @nrwl/workspace (luckily it has been restored since in Nx v11.3.0)

Maybe a Nx compatibility matrix page could be created and updated upon each potential breaking change? So that plugin authors can be aware ahead of time and proceeed or schedule the update of their plugins.

For example:

Nx version	Potential Breaking changes	Potential affected community plugins
v11.2.6	- removed @angular-devkit/{core,architect,schematics} dependencies	Plugins written with angular devkit API
v11.2.6	- rename utilities folder into @nrwl/workspace dependencies	Plugins using @nrwl/workspace utilities

Of course, the ideal solution would be to have these major updates reflected in the semantic versioning system of Nx, and not hidden as "minor" changes...

[tinesoft]

Just noticed this Wiki page: https://github.com/nrwl/nx/wiki/Breaking-Changes which is a good start.