Incomplete Ghost update procedure

The developer docs here (Ghost Docs) tell me to update my self-hosted Ghost with Ghost-CLI while disregarding the currently installed Ghost-CLI version.
The update script started by ghost update even instructs me to update Ghost-CLI beforehand, but then just continues on with the update without care.
A warning is a good idea, but not being able to act on it is not okay.
Why do you not stop the upgrade when you detect an out-of-date Ghost-CLI?
Or just ask the user if he wants to continue or abort?
Or have the step to update the Ghost-CLI BEFOREHAND clearly stated in the Docs, just like the backup before the upgrade?