Updating

You decide when

Your copy is yours, so nothing changes unless you bring it in. There is no forced upgrade and no switch-off date for a version you are happy with. Each release is listed in the changelog in plain English, with anything that needs action called out.

Updating code never changes your data. Your contacts, deals and messages live in your database, not in the code files. When a release does need a data change, it says so and gives you the command to run yourself.

The update helper

New versions arrive the same way as your first download. Unzip the new version, then run the helper from your project folder:

npx pnpm run update

Type run. A plain pnpm update is a different command that only bumps dependency versions.

• It shows what is new from the changelog in the download.
• It previews which files it will bring in and which it will keep, before it touches anything.
• It keeps your secrets, your history, your installed packages and any file you changed.
• It waits for you to type yes, never deletes files, and never deploys or migrates on its own.
• It finishes with a setup check to confirm everything is still connected.

Step by step

1. Take a backup you keep off-platform. See Backups.
2. Read the changelog from your current version forward.
3. Preview without changing anything: npx pnpm run update -- --dry-run --from path/to/new-version
4. Apply it, and type yes at the preview: npx pnpm run update -- --from path/to/new-version
5. If the helper says dependencies changed, run the install command it prints and commit the lockfile.
6. Try it on a development deployment and a preview build first. Sign in, open a contact, send a message and run a workflow.
7. Deploy the backend if it changed, then push the app so your host rebuilds it.
8. Run any migration last, only if the release asks for one, with a fresh backup in hand.

A skipped migration rarely shows an error. Instead, older data quietly looks missing or numbers look wrong. Every release says either what to run or that there is nothing to run, so check before you move on.

Rolling back

For code, redeploy the previous version or promote an earlier deployment on your host. For data, restore the backup you took before updating. That is why the backup step is not optional.