angular-cli: latest ver of npm is incorrect. It's 9.1.11 instead of 10.0.2

Hi all, we aware of the issue and will be addressed once a Googler in the US will be available to update tags of the packages. (Currently it’s still 4:33am).

Points of action:

• Update latest tag to point to v10.0.2
• Update v9-lts tag to point to v9.1.10

$ for pkg in @angular/{cli,pwa} @angular-devkit/{architect,architect-cli,build-optimizer,build-ng-packagr,build-angular,build-webpack,core,schematics,schematics-cli} @ngtools/webpack @schematics/{angular,schematics,update}; do echo "\n$pkg"; npm dist-tag ls $pkg; done

@angular/cli
latest: 9.1.11
next: 10.1.0-next.0
v6-lts: 6.2.9
v7-lts: 7.3.10
v8-lts: 8.3.28
v9-lts: 9.1.10

@angular/pwa
latest: 0.901.11
next: 0.1001.0-next.0
v6-lts: 0.8.9
v7-lts: 0.13.10
v8-lts: 0.803.28
v9-lts: 0.901.10

@angular-devkit/architect
latest: 0.901.11
next: 0.1001.0-next.0
v6-lts: 0.8.9
v7-lts: 0.13.10
v8-lts: 0.803.28
v9-lts: 0.901.10

@angular-devkit/architect-cli
latest: 0.901.11
next: 0.1001.0-next.0
v6-lts: 0.8.9
v7-lts: 0.13.10
v8-lts: 0.803.28
v9-lts: 0.901.10

@angular-devkit/build-optimizer
latest: 0.901.11
next: 0.1001.0-next.0
v6-lts: 0.8.9
v7-lts: 0.13.10
v8-lts: 0.803.28
v9-lts: 0.901.10

@angular-devkit/build-ng-packagr
latest: 0.901.11
next: 0.1001.0-next.0
v6-lts: 0.8.9
v7-lts: 0.13.10
v8-lts: 0.803.28
v9-lts: 0.901.10

@angular-devkit/build-angular
latest: 0.901.11
next: 0.1001.0-next.0
v6-lts: 0.8.9
v7-lts: 0.13.10
v8-lts: 0.803.28
v9-lts: 0.901.10

@angular-devkit/build-webpack
latest: 0.901.11
next: 0.1001.0-next.0
v6-lts: 0.8.9
v7-lts: 0.13.10
v8-lts: 0.803.28
v9-lts: 0.901.10

@angular-devkit/core
latest: 9.1.11
next: 10.1.0-next.0
v6-lts: 0.8.9
v7-lts: 7.3.10
v8-lts: 8.3.28
v9-lts: 9.1.10

@angular-devkit/schematics
latest: 9.1.11
next: 10.1.0-next.0
v6-lts: 0.8.9
v7-lts: 7.3.10
v8-lts: 8.3.28
v9-lts: 9.1.10

@angular-devkit/schematics-cli
latest: 0.901.11
next: 0.1001.0-next.0
v6-lts: 0.8.9
v7-lts: 0.13.10
v8-lts: 0.803.28
v9-lts: 0.901.10

@ngtools/webpack
latest: 9.1.11
next: 10.1.0-next.0
v6-lts: 6.2.9
v7-lts: 7.3.10
v8-lts: 8.3.28
v9-lts: 9.1.10

@schematics/angular
latest: 9.1.11
next: 10.1.0-next.0
v6-lts: 0.8.9
v7-lts: 7.3.10
v8-lts: 8.3.28
v9-lts: 9.1.10

@schematics/schematics
latest: 0.901.11
next: 0.1001.0-next.0
v6-lts: 0.8.9
v7-lts: 0.13.10
v8-lts: 0.803.28
v9-lts: 0.901.10

@schematics/update
latest: 0.901.11
next: 0.1001.0-next.0
v6-lts: 0.8.9
v7-lts: 0.13.10
v8-lts: 0.803.28
v9-lts: 0.901.10

I’ve also retagged v9-lts to point to v9.1.11

$ ./bin/devkit-admin dist-tag --version 9.1.11 --tag v9-lts
+v9-lts: @angular/cli@9.1.11
+v9-lts: @angular/pwa@0.901.11
+v9-lts: @angular-devkit/architect@0.901.11
+v9-lts: @angular-devkit/architect-cli@0.901.11
+v9-lts: @angular-devkit/build-angular@0.901.11
+v9-lts: @angular-devkit/build-ng-packagr@0.901.11
+v9-lts: @angular-devkit/build-optimizer@0.901.11
+v9-lts: @angular-devkit/build-webpack@0.901.11
+v9-lts: @angular-devkit/core@9.1.11
+v9-lts: @angular-devkit/schematics@9.1.11
+v9-lts: @angular-devkit/schematics-cli@0.901.11
+v9-lts: @ngtools/webpack@9.1.11
+v9-lts: @schematics/angular@9.1.11
+v9-lts: @schematics/schematics@0.901.11
+v9-lts: @schematics/update@0.901.11

Sorry about this! I’ve retagged all CLI packages, with latest = v10.0.2.

$ ./bin/devkit-admin dist-tag --version 10.0.2 --tag latest
+latest: @angular/cli@10.0.2
+latest: @angular/pwa@0.1000.2
+latest: @angular-devkit/architect@0.1000.2
+latest: @angular-devkit/architect-cli@0.1000.2
+latest: @angular-devkit/build-angular@0.1000.2
+latest: @angular-devkit/build-ng-packagr@0.1000.2
+latest: @angular-devkit/build-optimizer@0.1000.2
+latest: @angular-devkit/build-webpack@0.1000.2
+latest: @angular-devkit/core@10.0.2
+latest: @angular-devkit/schematics@10.0.2
+latest: @angular-devkit/schematics-cli@0.1000.2
+latest: @ngtools/webpack@10.0.2
+latest: @schematics/angular@10.0.2
+latest: @schematics/schematics@0.1000.2
+latest: @schematics/update@0.1000.2

I also saw, that the same issue with the version happened with @angular-devkit/core, @angular-devkit/schematics and @schematics/angular. Should I create a separate issue, to track that, or, it’s the all the same part of already reported one?

All Angular CLI packages are effected by this, this includes @schematics/* and @angular-devkit/ etc… so no need to open a new issue.

One of the workarounds if you are trying to ng update right now is to run ng update @angular/core@10 @angular/cli@10

Yeah, I’ve got errors now, when try to build with the latest version, like

This version of CLI is only compatible with Angular versions 0.0.0 || ^9.0.0-beta || >=9.0.0 <10.0.0,
but Angular version 10.0.3 was found instead.