detect and warn if angular is updated outside of ng update

[blathersbugs]

🚀 Feature request

Command (mark with an x)

• new
• build
• serve
• test
• e2e
• generate
• add
• update
• lint
• extract-i18n
• run
• config
• help
• version
• doc

Description

A clear and concise description of the problem or missing capability...

currently if someone updates angular using the package manager, migrations are not run

Describe the solution you'd like

detect if angular is updated outside of ng update and warn the user

If you have a solution in mind, please describe it.

a possible solution might be to add a field in angular.json that specifies the latest migrations that have been run (defaulting to the initially installed version), when a command like build is run, the cli can compare that to the installed version of angular and warn the user if migrations need to be run

Describe alternatives you've considered

Have you considered any alternative solutions or workarounds?

Obviously googling the error message or reading the docs before upgrading is the solution, but if this is easy enough to implement, it might be worth doing.

[angular-robot]

Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

Find more details about Angular's feature request process in our documentation.

[angular-robot]

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.