Alan Agius 1e9e890bb0 fix(@angular/cli): logic which determines which temp version of the CLI is to be download during ng update ...

Previously, when using an older version of the Angular CLI, during `ng update`, we download the temporary `latest` version to run the update. The ensured that when running that the runner used to run the update contains the latest bug fixes and improvements.

This however, can be problematic in some cases. Such as when there are API breaking changes, when running a relatively old schematic with the latest CLI can cause runtime issues, especially since those schematics were never meant to be executed on a CLI X major versions in the future.

With this change, we improve the logic to determine which version of the Angular CLI should be used to run the update.

Below is a summarization of this.

- When using the `--next` command line argument, the `@next` version of the CLI will be used to run the update.
- When updating an `@angular/` or `@nguniversal/` package, the target version will be used to run the update. Example: `ng update @angular/core@12`,  the update will run on most recent patch version of `@angular/cli` of that major version `@12.2.6`.
- When updating an `@angular/` or `@nguniversal/` and no target version is specified. Example: `ng update @angular/core` the update will run on most latest version of the `@angular/cli`.
- When updating a third-party package, the most recent patch version of the installed `@angular/cli` will be used to run the update. Example if `13.0.0` is installed and `13.1.1` is available on NPM, the latter will be used.

2021-11-23 07:44:53 +01:00

..

cli

feat(@angular/cli): officially support Node.js v16

2021-10-06 06:11:09 -05:00

config

fix(@angular/cli): generate new random user ID when passing empty string to uuid

2021-10-13 15:29:46 +02:00

init.ts

fix(@angular/cli): logic which determines which temp version of the CLI is to be download during ng update

2021-11-23 07:44:53 +01:00