Skip to main content
Condo follows semantic versioning. Minor and patch releases are backward compatible. Major versions may introduce breaking changes to APIs, data formats, or infrastructure requirements. Before upgrading any major version, review the corresponding guide below. The general process is:
1

Back up your data

Take a fresh backup of all databases (PostgreSQL and KV storage) before making any changes.
2

Stop running applications

Shut down all app and worker processes to prevent writes during migration.
3

Run migrations

Apply database and data migrations as described in the version guide.
4

Redeploy

Deploy the new version of the application and start workers.

Migration tool

Some migrations require @open-condo/migrator, a dedicated CLI tool for data migrations.
npm i -g @open-condo/migrator
See the individual version guides for the specific commands to run.

Available guides

Migrating to v3

Redis to Valkey support and KV key namespace isolation for multi-app setups.

Migrating to v4

Node.js 22 LTS, @open-keystone fork, Webpack 5, and CSS modules.

Migrating to v5

Heuristics-based address deduplication and updated news template placeholders.

Build docs developers (and LLMs) love