Skip to main content
Applies to: the upgrade to 6.2, for deployments with the bundled Valkey (8.1.9, or the legacy one-click 8.1.1 pin, → 9.1.2). Part of the 6.2 upgrade guide. Managed Redis/Valkey services follow their provider’s procedure.

Before

  • Schedule a brief service interruption and stop writers using the standard upgrade procedure.
  • Back up the Valkey volume and record its current image and configuration. Keep the existing volume.
  • Use the image/digest from your selected release’s Compose file or Helm values. Both linux/amd64 and linux/arm64 are supported; do not substitute a platform-specific digest.

During

Download the selected release. Copy only its redis image reference into your working Compose file, preserving local settings and mounts.
One-click updates replace only the legacy amd64-only 8.1.1 pin, with 9.1.2. They keep the 8.1.9 pin from 6.1 and custom pins, so a one-click install stays on 8.1.9 until you copy the redis image reference into formbricks/docker-compose.yml as above. The Compose backup still uses the historical .before-valkey-8.1.9 suffix.

After

Check Redis/Valkey connectivity, pending jobs and rate limiting before reopening traffic. Do not delete the volume or run FLUSHDB.

Recovery

Stop writers before recovery. Older Valkey versions may not read persistence files rewritten by version 9. Restore the pre-upgrade data backup with its matching image and configuration; reconcile pending work before restarting consumers. Source: Valkey image upgrade.