MokoConsulting/MokoCLI
Public Access
1
0
Fork 0
Code Issues 3 Pull Requests Packages Releases 8 Wiki Activity

docs: document auto-bump on all branches in multi-channel architecture

Browse Source 
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Jonathan Miller
2026-04-21 12:30:21 -05:00
parent 032c32637f
commit 14b4477ff2
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
templates/workflows/README.md
+2 -1
View File
@@ -495,7 +495,8 @@ Joomla extensions use `updates.xml` as their update server manifest. MokoStandar
- **Joomla filters by user setting** — Site administrators choose "Minimum Stability" in Joomla's update settings; Joomla shows updates matching that level or higher
- **SHA-256 must be raw hex** — No `sha256:` prefix. Joomla expects the raw hash value
- **Version format is zero-padded semver** — `XX.YY.ZZ` (e.g., `01.00.00`), not tag names like `v01`
- **All patches release** — Including patch `00`. The `sync-version-on-merge` workflow auto-bumps the patch on every merge to main
- **All patches release** — Including patch `00`. Release workflows auto-bump the patch version before building (increments `XX.YY.ZZ` → `XX.YY.(ZZ+1)` in README.md, manifest, and the matching updates.xml channel)
- **Auto-bump on all branches** — `release.yml` (manual dispatch) and `update-server.yml` (branch merges) both auto-bump patch before building. No manual version bump required
### Channel-to-Workflow Mapping