MokoConsulting/MokoOnyx

fix: align all version numbers to 02.08.00 #91

Merged

jmiller merged 4 commits from dev into main

2026-05-29 05:38:24 +00:00

Author	SHA1	Message	Date
gitea-actions[bot]	c1c9ea3ce3	chore: update development channel 02.08.00-dev [skip ci] Branch Cleanup / Delete merged branch (pull_request) Has been skipped Details Universal: Build & Release / Promote Pre-Release to RC (pull_request) Has been skipped Details Universal: Build & Release / Build & Release Pipeline (pull_request) Successful in 12s Details	2026-05-29 05:38:13 +00:00
gitea-actions[bot]	e74b053931	chore(version): auto-bump 02.08.00-dev [skip ci]	2026-05-29 05:38:12 +00:00
Jonathan Miller	2cfe54b85d	fix: align templateDetails.xml version to 02.08.00 (remove -dev suffix) [skip bump] Universal: Auto Version Bump / Version Bump (push) Has been skipped Details Generic: Repo Health / Site Health (push) Has been skipped Details Generic: Repo Health / Access control (push) Successful in 1s Details Update Server / Update Server (push) Successful in 9s Details Generic: Repo Health / Release configuration (push) Has been cancelled Details Generic: Repo Health / Scripts governance (push) Has been cancelled Details Generic: Repo Health / Repository health (push) Has been cancelled Details All version sources must match for Joomla update detection: templateDetails.xml, manifest.xml, and updates.xml. Authored-by: Moko Consulting Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-29 00:37:59 -05:00
Jonathan Miller	5670850258	fix: point dev stream to stable 02.08.00 (highest release) [skip ci] When stable is higher than dev, the development stream must also point to the stable release. Otherwise Joomla sees the lower dev version, picks stable as upgrade, installs it, but dev stream still shows lower version causing an update loop. Authored-by: Moko Consulting Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-05-29 00:33:35 -05:00