From 14b4477ff2fadf0dde2704b061ed6eb5253622fc Mon Sep 17 00:00:00 2001 From: Jonathan Miller Date: Tue, 21 Apr 2026 12:30:21 -0500 Subject: [PATCH] docs: document auto-bump on all branches in multi-channel architecture Co-Authored-By: Claude Opus 4.6 (1M context) --- templates/workflows/README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/templates/workflows/README.md b/templates/workflows/README.md index 8864d7c..35c95b6 100644 --- a/templates/workflows/README.md +++ b/templates/workflows/README.md @@ -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