ConverzaFlow upgrades

1. 1

   Read the target release notes

   Confirm PHP, MySQL 8, Composer, and extension requirements.

2. 2

   Backup

   Database, .env, storage uploads, custom modules, and local changes. Keep the previous code artifact.

3. 3

   Agree a maintenance window

   Name a rollback owner before you start.

php artisan down
php artisan queue:restart

# Replace application code with the new release.
# Preserve .env, approved uploads, supported local modules only.

composer install --no-dev --classmap-authoritative
php artisan migrate --force
php artisan optimize:clear
php artisan optimize
php artisan storage:link
php artisan up

• Do not merge old vendor, caches, or prebuilt assets into the new tree
• Restart Supervisor/systemd workers after upgrade
• Validate auth, queues, scheduler, mail, storage, and critical workflows

Code rollback alone may be unsafe after migrations. Restore the pre-upgrade database and uploads with the previous code artifact unless the release documents a reversible path.