Update a deployed release

Before updating, record the running image tags and database migration version, and verify a recent recovery set. Schedule the update around active conversations and queued campaigns.

Select a complete release

Use the image registry and release identifier supplied for your deployment. Keep the API and UI on compatible versions. If the release changes public routes, update the gateway alongside them. This v2 release requires both the backend mount and gateway routing for /api/v2/.

Deploy the intended immutable release tag to the matching services. For a Compose source deployment, use the files and build command in Linux installation.

Preserve state during the change

Retain existing data volumes, connection settings and authentication secrets. Review migration logs before returning traffic. Stopping a worker with an active voice connection can interrupt the call; use the drain mechanism configured by your deployment.

Check and recover

Verify login, a known record, model access and a controlled voice call. If the new release changes API v2, also test an authenticated read. Reverting an image does not reverse a database migration: restore or roll back only with a procedure compatible with the recorded schema version.