# Release Process {#release-process}


How releases are prepared, tested, and published.


## Versioning {#versioning}


Ever Gauzy follows [Semantic Versioning](https://semver.org/):

- **MAJOR** — breaking changes
- **MINOR** — new features (backward-compatible)
- **PATCH** — bug fixes


## Release Workflow {#release-workflow}






```mermaid
graph LR
    A[Develop] --> B[Release Branch]
    B --> C[Testing & QA]
    C --> D[Merge to Main]
    D --> E[Tag & Publish]
    E --> F[Docker Images]
    F --> G[NPM Packages]
```






### 1. Create Release Branch {#1-create-release-branch}


```bash
git checkout develop
git pull
git checkout -b release/1.5.0
```


### 2. Update Version {#2-update-version}


```bash
yarn version --new-version 1.5.0 --no-git-tag-version
```


### 3. Testing {#3-testing}


- Run full test suite
- Deploy to staging environment
- Manual QA verification


### 4. Merge & Tag {#4-merge--tag}


```bash
git checkout main
git merge release/1.5.0
git tag -a v1.5.0 -m "Release 1.5.0"
git push origin main --tags
```


### 5. Automated Publish {#5-automated-publish}


CI/CD pipelines automatically:

- Build Docker images
- Publish to GHCR
- Publish NPM packages
- Deploy to production


## Release Artifacts {#release-artifacts}


| Artifact      | Registry / Location            |
| ------------- | ------------------------------ |
| Docker Images | `ghcr.io/ever-co/gauzy-*`      |
| NPM Packages  | `packages.ever.co` (Verdaccio) |
| Desktop Apps  | GitHub Releases                |


## Related Pages {#related-pages}


- [Git Workflow](https://sourcey-gauzy.pages.dev/development/git-workflow/index.md) — branching model
- [Contributing](https://sourcey-gauzy.pages.dev/development/contributing/index.md) — contribution guide
- [Private Registry](https://sourcey-gauzy.pages.dev/devops/private-registry/index.md) — Verdaccio