Deploy & runGuide

Update your install

Most versions need nothing from you besides pulling the new images. When one does, its entry on the versions page says so at the top, with the exact line to paste. Admins also see a small notice in the app when a newer version is out.

4 min readBefore this: Self-host with Docker Compose
What you will learn
  • Find out whether a version asks anything of you
  • Update with Docker Compose or Helm
  • Turn off the new-version notice

Before you update

Open the versions page and pick the version you run in Your version. A box above the list gathers every step between it and the newest, in the order to do them. If the box says there is nothing to do, go straight to the commands below.

Your running version is on Settings → Billing, and in WAISO_VERSION if you pinned one in .env.

waiso1.7.0 is out · one step before updatingRead itA
1.7.01 December 2026
Action needed before you updateBeforeAdd the new setting to .env.WAISO_EXAMPLE=on
Update commandsComposeHelm
The notice names the newest version and whether it asks something; its entry says what, with the line to paste.

Versions are numbered major.minor.patch. A patch fixes the version before it. A minor adds things you can use, and is where a step is most likely. A major would change how an install is run, and would come with its own guide.

Updating skips nothing: going from 1.4.0 to 1.6.1 in one go is fine, as long as you do the steps the box lists for every version in between. There is no need to stop at each version on the way.

Docker Compose

Set the version in .env (or leave WAISO_VERSION unset to follow the compose file you have), then pull and restart. The API applies its own database changes when it starts.

Shellterminal
# .env
WAISO_VERSION=1.6.1

docker compose pull && docker compose up -d --remove-orphans

--remove-orphans stops services a newer version no longer has. If a version changed the compose file itself, its entry says to fetch the new one first.

Kubernetes (Helm)

Shellterminal
helm upgrade waiso oci://ghcr.io/talissonjunior16/charts/waiso --version 1.6.1 --reuse-values

--reuse-values keeps your settings. A step that adds a setting tells you the value to add under api.env or the key it belongs to.

If something looks wrong after updating

  • Check that every service runs the same version: docker compose ps lists the image tags. A worker left on the old version picks up runs the new API no longer expects.
  • Read the API log from its start: docker compose logs api. Database changes are applied there, and a problem with one is written in plain words.
  • Reload the browser tab, so it loads the new web app instead of the one it kept open.

The new-version notice

Every 12 hours the API reads https://waiso.dev/changelog/latest.json, a public file with the list of versions. The request carries nothing about your install. When a newer version exists, admins see a small notice in the top bar that links to its entry; nobody else sees it, and it can be hidden until the next version.

  • Docker Compose: set WAISO_UPDATE_CHECK=off in .env.
  • Helm: add WAISO_UPDATE_CHECK: "off" under api.env.

Related topics