Software update information

How Laundrix is versioned and how to move to a new release without losing data.

Versioning

Release type	Example	What to expect
Patch	1.0.1	Bug and security fixes. Safe to apply promptly.
Minor	1.1.0	New features that keep existing behaviour. May add database tables or columns.
Major	2.0.0	May change behaviour or settings. Read the release notes first.

The version number is in package.json and every release is described in the release notes and in CHANGELOG.md.

Before you update

Back up the database and, if you store files locally, the UPLOAD_DIR folder. With Neon, create a branch or confirm point-in-time recovery is on.
Read the release notes for every version between yours and the new one.
Update a staging copy first if you have one, and run through a few real orders.
Keep a note of your current version so you can return to it.

Update steps

Stop the application (or schedule a short maintenance window).
Replace the code with the new version, or pull it if you use Git. Keep your own .env file.
Install dependencies:
```
npm install
```
Apply database changes. Migrations are additive and safe to re-run:
```
npx prisma migrate deploy
npx prisma generate
```
On Vercel, run npx prisma migrate deploy from your computer against the direct Neon connection string before or right after deploying.
Build and start:
```
npm run build
npm start
```
Docker users run docker compose up --build -d. On Vercel, deploy as usual.
Check /api/health returns {"status":"ok"}, then sign in and open the dashboard.

Run migrations before traffic hits new code

If a new version reads a new column that the database does not have yet, parts of the app will fail. The sign-in page, for example, shows a developer note when its company list cannot load. Running npx prisma migrate deploy fixes this.

After you update

Sign in as an owner and place a test order, print its tags, and take a test payment.
Check that file uploads still work and that background jobs still run (the jobs endpoint returns a summary).
Review the startup log for configuration warnings.
If something is wrong, restore the backup and redeploy the previous version. Migrations are additive, so older code normally still runs against a newer schema, but restoring the backup is the safe route.

If you customised the code

Merge the new release into your branch rather than overwriting your changes. Re-run the tests (npm run check) and the browser scripts (npm run smoke, npm run e2e) after merging.

Update support

What support and future updates are included depends on the licence and listing you purchased. Contact the support address shown in the footer of the website with your version number and a description of the problem.