Release Process
How releases are prepared, tested, and published.
Versioningβ
Ever Gauzy follows Semantic Versioning:
- MAJOR β breaking changes
- MINOR β new features (backward-compatible)
- PATCH β bug fixes
Release Workflowβ
1. Create Release Branchβ
git checkout develop
git pull
git checkout -b release/1.5.0
2. Update Versionβ
yarn version --new-version 1.5.0 --no-git-tag-version
3. Testingβ
- Run full test suite
- Deploy to staging environment
- Manual QA verification
4. Merge & Tagβ
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β
CI/CD pipelines automatically:
- Build Docker images
- Publish to GHCR
- Publish NPM packages
- Deploy to production
Release Artifactsβ
| Artifact | Registry / Location |
|---|---|
| Docker Images | ghcr.io/ever-co/gauzy-* |
| NPM Packages | packages.ever.co (Verdaccio) |
| Desktop Apps | GitHub Releases |
Related Pagesβ
- Git Workflow β branching model
- Contributing β contribution guide
- Private Registry β Verdaccio