ng update shows confusing messages when there's nothing recommended

[StephenFluin]

Versions

Angular CLI: 6.0.0-rc.2
Node: 9.2.0
OS: linux x64
Angular: 6.0.0-rc.3
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

@angular/cli: 6.0.0-rc.2
@angular-devkit/architect: 0.5.4
@ngtools/json-schema: 1.2.0
@schematics/update: 0.5.4
typescript: 2.9.0-dev.20180409
webpack: error

Repro steps

1. Have a fully up to date project (do everything ng update --next tells you to do)
2. run ng update --next

Observed behavior

$ ng update --next
    We analyzed your package.json, there are some packages to update:
    
      Name                               Version                    Command to update
     ---------------------------------------------------------------------------------------------------------
    
    
    There might be additional packages that are outdated.
    Or run ng update --all to try to update all at the same time.
    
Nothing to be done.

Desired behavior

This advice seems contradictory. It's unclear what I should be doing next as a user.

If the CLI thinks everything is good to go, then it should say something like 'All of your packages are up to date and we can't find anything that needs to be updated'.

[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.}