1. Back up first — both halves. Export the database and copy the whole application folder, including .env and storage/app/public. Nothing below is risky, but an update you cannot reverse is the one that goes wrong.
2. Read the release notes above. Anything needing manual action is called out there. If you skipped versions, read every entry between yours and the latest — they are cumulative.
3. Download the package. From your account. Verify the SHA-256 shown next to the download against your copy before you unpack it.
4. Put the site into maintenance mode. Run php artisan down so no order is written while files are half-replaced.
5. Copy the new files over. Replace everything except .env, your storage/ directory and any file you have customised. If you edited core files, compare them with the new ones rather than overwriting — this is why the release lists changed files.
6. Update dependencies and the database. composer install --no-dev -o, then php artisan migrate --force. Migrations only ever add to your data; they do not drop it.
7. Clear the caches. php artisan optimize:clear, then rebuild with php artisan config:cache route:cache. Skipping this is the single most common cause of "the update did nothing".
8. Bring it back up and check. php artisan up, then place one test order end to end — checkout, seller notification, rider assignment, delivery.
9. Rebuild the apps only if the notes say so. Most releases are backend-only. When a release does change the Flutter apps, bump the version, rebuild and submit to the stores as usual.

Updating a live business and would rather we did it? Updates are part of our installation service — ask for a quote. If an update goes wrong and you have support, open a ticket and we will get you back up.