aWhere Manual
Install and run a site

Upgrade stops

How far an upgrade can skip, and what to do when awhere upgrade tells you to upgrade to another Release first

An upgrade stop is a Release that a site must upgrade to before it can upgrade to anything newer. You do not have to remember them: awhere upgrade tells you before it changes anything.

How far you can skip

  • If the major Release (the first number) stays the same, you can skip freely. For example, you can go from 5.0.0 straight to 5.4.2.
  • If the major Release changes, first upgrade to the last Release of the old major Release. For example, to go from 5.x to 6.0.0, upgrade to the latest 5.x, wait for its Migrations to finish, and then go to 6.0.0.

No Release is an upgrade stop yet.

If you meet an upgrade stop

awhere upgrade stops without changing anything and tells you which Release to upgrade to first. For example (an invented example):

database `datastore` has data but has not applied Migration `2026-02-01-core-example`, which release 6.0.0 no longer carries (release 5.9.0 was the last that did); upgrade to release 5.9.0 first and let its Migrations finish, then this one.

Do this.

  1. awhere upgrade 5.9.0
  2. Open the System page and wait until no Migration shows Running or Failed.
  3. awhere upgrade 6.0.0

A site installed new from Release 6.0.0 or later never sees this message.

On this page