Release Policy
이 콘텐츠는 아직 번역되지 않았습니다.
Actionbase follows Semantic Versioning (SemVer) to communicate changes clearly.
Version scheme
Section titled “Version scheme”Versions follow the format MAJOR.MINOR.PATCH:
- MAJOR: Incompatible API changes
- MINOR: New features, backward compatible
- PATCH: Bug fixes, backward compatible
Example: 1.2.3 → Major 1, Minor 2, Patch 3
Current stage (0.x.x)
Section titled “Current stage (0.x.x)”Actionbase has been running in production internally at Kakao. The open-source release is in preparation. During the 0.x.x phase:
- APIs may change between releases
- Installation and operations guides are being prepared
- Feedback and experimentation are welcome
The 1.0.0 release will mark the point where external users can deploy Actionbase in production environments.
Compatibility promise
Section titled “Compatibility promise”The following applies after 1.0.0:
- PATCH releases are always safe to upgrade
- MINOR releases add features without breaking existing functionality
- MAJOR releases may include breaking changes; migration guides will be provided
Release candidates
Section titled “Release candidates”Before a release, one or more release candidates (-rc.N) may be published for community testing and feedback.
To participate:
- Test RC versions in non-production environments
- Report issues on GitHub Issues
- Share feedback on GitHub Discussions
Support policy
Section titled “Support policy”Currently, only the latest release is actively supported with bug fixes and security patches.
As the project matures, we may introduce Long-Term Support (LTS) releases with extended maintenance windows.
Release artifacts
Section titled “Release artifacts”All modules share the same version and are released together.
| Module | Artifact | Distribution |
|---|---|---|
| core | Java library | GitHub Packages (Maven Central after 1.0.0) |
| server | Docker image | ghcr.io/kakao/actionbase |
| cli | Binary | GitHub Releases |
Release announcements are posted in GitHub Releases.