ng update says "project has been updated to v9" even if already on v9

[gkalpak]

🐞 Bug report

Command (mark with an x)

• new
• build
• serve
• test
• e2e
• generate
• add
• update
• lint
• xi18n
• run
• config
• help
• version
• doc

Is this a regression?

No idea.

Description

While updating angular.io from Angular 9.0.0 to 9.1.0-next.5 (as part of angular/angular#36145), using ng update @angular/core --next, I got the following message at the end (which is a little confusing -and likely unintended- since I was already on v9):

Your project has been updated to Angular version 9!
For more info, please see: https://v9.angular.io/guide/updating-to-version-9

🌍 Your Environment

Angular CLI: 9.1.0-next.4
Node: 12.15.0
OS: win32 x64

Angular: 9.1.0-next.5
... animations, common, compiler, compiler-cli, core, elements
... forms, language-service, platform-browser
... platform-browser-dynamic, router, service-worker
Ivy Workspace: Yes

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.901.0-next.4
@angular-devkit/build-angular     0.901.0-next.4
@angular-devkit/build-optimizer   0.901.0-next.4
@angular-devkit/build-webpack     0.901.0-next.4
@angular-devkit/core              9.1.0-next.4
@angular-devkit/schematics        9.1.0-next.4
@angular/cdk                      9.1.3
@angular/cli                      9.1.0-next.4
@angular/material                 9.1.3
@ngtools/webpack                  9.1.0-next.4
@schematics/angular               9.1.0-next.4
@schematics/update                0.901.0-next.4
rxjs                              6.5.4
typescript                        3.8.3
webpack                           4.42.0

[gkalpak]

cc @filipesilva

[dgp1130]

Alan looked into this recently, should have the necessary context.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}