Open-source software for Joomla, Gitea, and web platforms. Home of MokoSuite, MokoGitea, and MokoCLI.
Tennessee
releases/versioning
Versioning
Semantic versioning standards per platform.
Semantic Versioning 2.0
All MokoConsulting projects follow SemVer 2.0.0:
MAJOR.MINOR.PATCH
MAJOR — breaking changes (incompatible API/schema changes)
MINOR — new features (backwards-compatible additions)
PATCH — bug fixes (backwards-compatible fixes)
Joomla Extensions
Joomla uses two-digit segments: XX.YY.ZZ
01.00.00 # Initial release
01.01.00 # Feature addition
01.01.01 # Bug fix
02.00.00 # Breaking change (schema migration required)
- Version in
manifest.xml<version>tag - SQL update scripts named to match:
sql/updates/mysql/01.01.00.sql - Git tags:
v1.1.0(standard semver, Joomla version in manifest)
MokoGitea
Fork versioning tracks upstream: v{upstream_major}.{moko_major}.{moko_minor}
v1261.0.0 # Based on Gitea 1.26.1, initial MokoGitea release
v1261.1.0 # New MokoGitea feature on same upstream base
v1261.1.1 # MokoGitea bugfix
v1270.0.0 # Rebased to Gitea 1.27.0
MCP Servers
Standard semver in package.json. No published releases — versioning is informational since servers deploy from monorepo main branch.
Standard semver in module descriptor $this->version:
1.0.0 # Initial release
1.1.0 # New feature
Pre-release Versions
v1.0.0-alpha.1 # Alpha: feature-incomplete, expect breakage
v1.0.0-beta.1 # Beta: feature-complete, fixing bugs
v1.0.0-rc.1 # Release candidate: ready unless blockers found
When to Bump
| Change | Version Bump |
|---|---|
| New feature, backwards-compatible | MINOR |
| Bug fix | PATCH |
| Database schema change (additive) | MINOR |
| Database schema change (breaking) | MAJOR |
| API endpoint added | MINOR |
| API endpoint removed/changed | MAJOR |
| Configuration format change | MAJOR |
| PHP version requirement change | MAJOR |
| New dependency added | MINOR |
| Security fix | PATCH (expedited release) |
Pages