MokoConsulting/moko-platform

chore: cascade main → dev (`81351f4`) [skip ci] #132

Merged

jmiller merged 1 commits from main into dev

2026-05-26 03:50:22 +00:00

Author	SHA1	Message	Date
Jonathan Miller	81351f45fd	fix: updates_xml_build — tag 'dev' not 'development', client for all types Generic: Repo Health / Site Health (push) Has been skipped Details Generic: Repo Health / Access control (push) Successful in 3s Details Universal: Cascade Main → Dev / Cascade main → branches (push) Successful in 8s Details Generic: Repo Health / Release configuration (push) Successful in 11s Details Generic: Repo Health / Scripts governance (push) Successful in 5s Details Generic: Repo Health / Repository health (push) Successful in 15s Details Platform: moko-platform CI / Gate 1: Code Quality (push) Successful in 1m25s Details Platform: moko-platform CI / Gate 5: Template Integrity (push) Failing after 14s Details Platform: moko-platform CI / Gate 4: Governance (push) Successful in 1m14s Details Platform: moko-platform CI / Gate 2: Unit Tests (8.2) (push) Successful in 1m19s Details Platform: moko-platform CI / Gate 2: Unit Tests (8.1) (push) Successful in 1m27s Details Platform: moko-platform CI / Gate 3: Self-Health Check (push) Failing after 1m27s Details Platform: moko-platform CI / Gate 2: Unit Tests (8.3) (push) Successful in 1m29s Details Platform: moko-platform CI / CI Summary (push) Has been cancelled Details Two root causes of Joomla updater not finding MokoWaaS updates: 1. stabilityTagToInteger('development') looks for STABILITY_DEVELOPMENT which doesn't exist → defaults to STABLE. Changed to 'dev' which maps to STABILITY_DEV (0). 2. Missing <client> tag defaults to client_id=1 (administrator) in Joomla's ExtensionAdapter. Packages install with client_id=0 (site). Now adds <client>site</client> for all extension types. Fixes: #129 Authored-by: Moko Consulting Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-25 22:50:07 -05:00