Related to #1635
After releasing CLI as @pnp/microsoft365-cli, we should deprecate the @pnp/office365-cli package to make it clear that it will no longer be updated.
Do we really want to deprecate all v2 versions on npm or do we leave them be and update the readme pointing people to the new package name?
@pnp/cli-for-microsoft-365-maintainers
What would be the reason not to deprecate? 馃
I would say deprecate v2, any fixes and new features will go into v3 from now on anyway and users would have to use the new package to get new updates.
I just noticed that there is a way to deprecate the whole package rather than a specific version, so perhaps that would be clearer then.
Deprecating a package will show a warning similar to following on top of the package page:

In the deprecation message we can point to the new package name and we can leave all versions as-is in case someone needs them for one reason or another.
Done
Most helpful comment
Done