Update from command line -- then again at web interface!

Nextcloud version 11.0.3
Operating system and version Centos 7
Apache 2.4.6
PHP version 5.6.31
Is this the first time you’ve seen this error?: Yes

The issue you are facing:

Today I did the upgrade from 11.0.3 to 12.0.0 using the command line, so:

sudo -u apache php /var/www/html/nextcloud/updater/updater.phar -vv

…which went well. “Upgrade of code successful.” Conveniently, it offered to do the next step automatically (normally I would execute sudo -u apache php /var/www/html/nextcloud/occ upgrade)

Should the "occ upgrade" command be executed? [Y/n] y
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
Set log level to debug
Updating database schema
Updated database
Disabled 3rd-party app: templateeditor
Updating <federatedfilesharing> ...
Updated <federatedfilesharing> to 1.2.0
<snip>
Checking for update of app workflowengine in appstore
Checked for update of app "workflowengine" in appstore 
Starting code integrity check...
Finished code integrity check
Update successful
Maintenance mode is kept active
Reset log level

Keep maintenance mode active? [y/N] n

Maintenance mode is disabled

So from there I was thinking I was all done. But when I went to login to the Nextcloud system via standard web interface, I was greeted by a button to push to UPDATE. There was nothing to be done but push it. I did, and it went through the same update steps again, I could see in the detailed log on the web page. The only difference was it mentioned at the end (about disabling bruteforcesettings):

Starting code integrity check
Finished code integrity check
Turned off maintenance mode
Reset log level
Following apps have been disabled: bruteforcesettings (3rdparty)

After this second upgrade process it began working as usual, and was at version 12.0.0.

If the update needed to be repeated, couldn’t the command line updater tell me this so I could run it again? It did confirm “Update Successful” so why did it need to run again?

Thanks.