Release Management Workflow
Plan, build, and ship releases.
Release Process
Version Numbering
Gauzy follows Semantic Versioning (SemVer):
| Type | Format | Example | When |
|---|---|---|---|
| Major | X.0.0 | 2.0.0 | Breaking changes |
| Minor | 0.X.0 | 1.5.0 | New features |
| Patch | 0.0.X | 1.5.3 | Bug fixes |
Release Checklist
Pre-Release
- All features merged to
develop - All tests passing
- Version bumped in
package.json - Changelog updated
- Documentation updated
- Database migrations tested
Release Day
- Create release branch from
develop - Final QA on staging
- Tag release in Git
- Build Docker images
- Deploy to production
- Verify health checks
- Monitor error rates
Post-Release
- Merge release branch to
main - Merge back to
develop - Announce release
- Update documentation site
- Close related issues/PRs
Rollback Process
If critical issues found:
- Revert to previous Docker image tag
- Or:
kubectl rollout undo deployment/gauzy-api - Investigate and fix
- Re-release as patch
Related Pages
- CI/CD Pipeline — CI/CD
- Blue-Green Deployment — zero-downtime
- Hotfix Workflow — emergency fixes