Updating the Project
Safely pulling and applying new versions
Backend Update Process
Run these commands in order from your pos-backend directory:
Frontend Update Process
Vercel (auto-deploy)
Push to main — Vercel detects the change and redeploys automatically. No manual action required.
Self-hosted
Warning
Always run npm run db:migrate:prod after a backend update. New features
often require new database columns or tables. Skipping this causes runtime
errors.
Reading the Changelog
Every release is documented in CHANGELOG.md at the repository root. Read it before every update. It lists:
- New features
- Bug fixes
- Breaking changes
- Any required manual migration steps
When a breaking change is listed, follow the migration instructions carefully before restarting the server.