Release Process

📦 Release Process

eOzka organization uses automated CI/CD pipelines to ensure safe and predictable releases.

Versioning

We follow Semantic Versioning (MAJOR.MINOR.PATCH).

• MAJOR version when you make incompatible API changes.
• MINOR version when you add functionality in a backwards compatible manner.
• PATCH version when you make backwards compatible bug fixes.

Release Workflow

1. Alpha/Beta Testing: Large features are merged into a develop or beta branch first.
2. Release Candidate: A release branch is cut and deployed to staging.
3. Tagging: A version tag (e.g., v1.2.0) is created on GitHub.
4. Publishing: GitHub Actions automatically builds and publishes the artifacts (NPM packages, Docker images, APKs).