git pullwhich will update the necessary files in the new version of the CMS.
composer requireto pull in the CMS, continue on after clicking on upgrade to proceed with the update. If anything failed, there should be a rollback that occurs. Otherwise, you may need to manually look at any files that changed. We highly recommend setting up the CMS in a git repo under your control, especially since running
git statuscan quickly help you find any issues that popped up.
yarn run prodto ensure the latest UI has been built for the admin and public side.