Consider the following scenario.
I have a solution created on 1.3.4.
I run the upgrade command, get the report, make all the updates.
Now I want to make sure I didn't forget anything so I downgrade the yo rc to 1.3.4, run the command again.
Now the report is instructing me to "update" all the @microsoft/ packages to 1.4.1.
We haven't tested this scenario although I can totally understand why you'd want to do it. When upgrading the project initially, did you upgrade to 1.5.0 or to 1.4.1?
To 1.5.0
Check. To what extent do you think this is related to #501?
I don't think it is. At this point I had fully ran my migration including making sure package and package lock were updated. I just wanted to run a final check to see if I didn't forget anything.
I'll have another look after I fixed #501 and see if I can repro it.
I can repro it and understand why it's happening. Working on a fix.
Fixed the bug in the latest beta, which should be released in a matter of days as v1.4.0. Thanks again for reporting the bug @baywet!