Upgrade Checklist
Step-by-step checklist for upgrading Ever Gauzy versions.
Pre-Upgradeβ
- Read release notes β Check changelog for breaking changes
- Backup database β Full pg_dump before any upgrade
- Test on staging β Never upgrade production first
- Check Node.js version β Verify compatible Node.js version
- Review migration files β Check for new database migrations
- Review env changes β Check for new/renamed environment variables
- Notify team β Announce maintenance window
During Upgradeβ
1. Pull Latest Codeβ
git fetch origin
git checkout v1.X.X # or latest tag
2. Install Dependenciesβ
yarn install --frozen-lockfile
3. Run Migrationsβ
# TypeORM
yarn typeorm migration:run
# MikroORM
npx mikro-orm migration:up
4. Buildβ
yarn build:api
yarn build
5. Deployβ
# Docker
docker compose pull
docker compose up -d
# Kubernetes
kubectl set image deployment/gauzy-api api=ghcr.io/ever-co/gauzy-api:v1.X.X
Post-Upgradeβ
- Verify health β
curl /api/health - Check logs β No unexpected errors
- Test key features β Login, time tracking, invoicing
- Monitor metrics β Error rates, response times
- Verify data β Spot-check recent records
- Update documentation β If internal docs reference version
Rollback Planβ
If issues found:
- Revert database migrations
- Deploy previous image/tag
- Verify service health
- Investigate root cause
See Rollback Strategies for details.
Related Pagesβ
- Release Management β release process
- Rollback Strategies β rollback
- TypeORM Migrations β migrations