# Release Management Workflow {#release-management-workflow}


Plan, build, and ship releases.


## Release Process {#release-process}






```mermaid
graph LR
    Dev[develop] -->|Feature freeze| RC[Release Candidate]
    RC --> QA[QA Testing]
    QA -->|Pass| Tag[Tag Release]
    QA -->|Fail| Fix[Fix & Retest]
    Fix --> QA
    Tag --> Build[Build Artifacts]
    Build --> Deploy[Deploy to Prod]
    Deploy --> Monitor[Monitor]
```






## Version Numbering {#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 {#release-checklist}



### Pre-Release {#pre-release}


- [ ] All features merged to `develop`
- [ ] All tests passing
- [ ] Version bumped in `package.json`
- [ ] Changelog updated
- [ ] Documentation updated
- [ ] Database migrations tested


### Release Day {#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 {#post-release}


- [ ] Merge release branch to `main`
- [ ] Merge back to `develop`
- [ ] Announce release
- [ ] Update documentation site
- [ ] Close related issues/PRs


## Rollback Process {#rollback-process}


If critical issues found:

1. Revert to previous Docker image tag
2. Or: `kubectl rollout undo deployment/gauzy-api`
3. Investigate and fix
4. Re-release as patch


## Related Pages {#related-pages}


- [CI/CD Pipeline](https://sourcey-gauzy.pages.dev/deployment/ci-cd/cicd-pipeline-guide/index.md) — CI/CD
- [Blue-Green Deployment](https://sourcey-gauzy.pages.dev/devops/blue-green-deployment/index.md) — zero-downtime
- [Hotfix Workflow](https://sourcey-gauzy.pages.dev/workflows/hotfix/index.md) — emergency fixes