Upgrade

Upgrading an installer-based deployment

The online installer supports fresh installations only and refuses nonempty directories. Re-running it is not an upgrade or rollback procedure. Do not delete an existing installation to bypass this check.

Before a manual upgrade, back up the database, Lens data and installation configuration, and review the target release's migration requirements. Automated configuration preservation, migration and rollback are not provided. Use the installed lensctl.sh to manage services; see Migration for database migration procedures.

Upgrading a from-source development checkout

git pull
npm install
python3 -m pip install -e 'apps/backend[dev]'
node scripts/generate-mcp-tools.mjs
scripts/lens-local.sh restart

scripts/lens-local.sh restart regenerates and validates the reuse map, and regenerates the MCP tool catalog, before restarting services.

Rolling back

The online installer does not implement rollback. For source-based development, switch to the previous tag/commit and rebuild its dependencies before restarting. Code rollback alone does not undo database migrations; follow the release's migration guidance or restore a compatible backup rather than assuming a single downgrade step is sufficient.