Files
moko-platform/cli
Jonathan Miller d96c5ac420
Platform: moko-platform CI / Gate 2: Unit Tests (8.1) (push) Blocked by required conditions
Platform: moko-platform CI / Gate 2: Unit Tests (8.2) (push) Blocked by required conditions
Platform: moko-platform CI / Gate 2: Unit Tests (8.3) (push) Blocked by required conditions
Platform: moko-platform CI / Gate 3: Self-Health Check (push) Blocked by required conditions
Platform: moko-platform CI / Gate 4: Governance (push) Blocked by required conditions
Platform: moko-platform CI / Gate 5: Template Integrity (push) Blocked by required conditions
Platform: moko-platform CI / CI Summary (push) Blocked by required conditions
Generic: Repo Health / Release configuration (push) Blocked by required conditions
Generic: Repo Health / Scripts governance (push) Blocked by required conditions
Generic: Repo Health / Repository health (push) Blocked by required conditions
Generic: Repo Health / Site Health (push) Has been skipped
Generic: Repo Health / Access control (push) Successful in 1s
Platform: moko-platform CI / Gate 1: Code Quality (push) Failing after 58s
fix: remove lesser stream copies, each stream updates independently
Joomla picks the HIGHEST version via version_compare() across ALL
entries. Lesser stream copies (02.17.00-dev) at the same base version
as stable (02.17.00) would never be selected because dev < stable.

Each stream now updates only when its own release happens:
- stable: on merge to main
- dev: on auto-bump after dev recreated from main
- rc: on promote-rc

The dev stream naturally gets 02.17.01-dev (higher than 02.17.00)
because auto-bump runs on the recreated dev branch.

Also sorts updates.xml entries dev→stable (dev first).

Authored-by: Moko Consulting
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-05-30 19:53:47 -05:00
..