feat: manifest.xml as canonical version source #168

Merged

jmiller merged 9 commits from dev into main 2026-05-26 20:08:03 +00:00

Conversation 0 Commits 9 Files Changed 33

+2808 -287

jmiller commented 2026-05-26 20:04:47 +00:00

Owner

Copy Link

Copy Source

Summary

• version_bump.php inserts into manifest.xml when missing
• version_read.php backfills from fallback sources
• Schema XSD now carries version attribute (09.01.00)
• All manifest.xml files get xsi:schemaLocation pointing to schema on main

Test plan

• Run version_read.php on repo without in manifest.xml
• Run version_bump.php on repo without in manifest.xml
• Verify schema validates with xmllint

## Summary - version_bump.php inserts <version> into manifest.xml when missing - version_read.php backfills <version> from fallback sources - Schema XSD now carries version attribute (09.01.00) - All manifest.xml files get xsi:schemaLocation pointing to schema on main ## Test plan - [ ] Run version_read.php on repo without <version> in manifest.xml - [ ] Run version_bump.php on repo without <version> in manifest.xml - [ ] Verify schema validates with xmllint

jmiller added 9 commits 2026-05-26 20:04:48 +00:00

Merge pull request 'chore: cascade main → dev (1fe4f83) [skip ci]' (#141) from main into dev ... 21acb19fed

chore: cascade main → dev [skip ci]

fix(updates_xml): treat 'development' and 'dev' as same channel in preservation ... 005eb5cf39

Legacy/manual entries used <tag>development</tag> while the CLI writes
<tag>dev</tag>. Without this alias, old entries survived preservation
and created duplicate dev channel entries.

Authored-by: Moko Consulting
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

fix(updates_xml): restore <client>site</client> for all extension types ... f441a8a51f

Joomla requires the client tag to match updates to installed extensions.
Without it, extension_id=0 in #__updates and the update is invisible.

Authored-by: Moko Consulting
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Merge pull request 'chore: cascade main → dev (c5e4b41) [skip ci]' (#165) from main into dev ... 320b2c57be

chore: cascade main → dev [skip ci]

Merge pull request 'chore: cascade main → dev (f8c28f0) [skip ci]' (#166) from main into dev ... 420b4f5f3c

chore: cascade main → dev [skip ci]

feat: release promotion pipeline, 5 new CLI tools, workflow refactoring ... 07ea171af9

New CLI tools:
- manifest_element.php — extract element/type/prefix from any platform manifest
- release_create.php — create/overwrite Gitea releases with proper naming
- release_package.php — build ZIP+tar.gz, SHA-256, upload assets
- release_promote.php — promote releases between channels (dev→RC→stable)
- version_reset_dev.php — reset platform version on dev branch after release

Updated CLI tools:
- version_bump.php — now writes to manifests, Dolibarr mod, composer.json (not just README)
- release_cascade.php — added --version for version-aware deletion of stale releases
- release_validate.php — auto-detect platform, --github-output, source dir check

Workflow changes (auto-release.yml):
- Draft PR to main → auto-promote highest pre-release to RC
- Merged PR to main → promote RC to stable (skip rebuild when RC exists)
- Removed paths filter for Go/Node/generic repo compatibility
- Fixed cascade --api-base parameter bug

Workflow changes (pre-release.yml):
- Auto-trigger development pre-release on feature branch merge to dev
- Removed paths filter

Infrastructure:
- RepositorySynchronizer: fixed template repo names, .mokogitea/workflows path,
  universal workflow cascade (Template-Generic → other templates)
- bulk_sync.php: syncs universal workflows to templates before repo sync
- PHPDoc added to 4 classes missing class-level docs
- Version bump 09.00.00 → 09.01.00

Closes #152 #153 #154 #155 #156 #157 #158 #159 #161 #162

Authored-by: Moko Consulting
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

refactor: pre-release.yml uses CLI tools instead of inline logic ... 1dba0c37b9

Replace 3 blocks of inline bash/PHP with existing CLI tool calls:
- Platform detection: manifest_read.php --github-output
- Element detection: manifest_element.php --github-output (28 lines → 4 lines)
- updates.xml update: updates_xml_build.php (25 lines → 3 lines)

Removes ~75 lines of duplicated inline logic. Workflow now delegates
all platform-aware logic to moko-platform CLI tools.

Closes #163

Authored-by: Moko Consulting
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

feat: release_mirror.php — mirror Gitea releases to GitHub ... 48d574e225

New CLI tool that mirrors a Gitea release (with assets) to a GitHub
repository. Replaces the 40-line inline bash in auto-release.yml Step 9.

Supports create/update, asset download+upload, and proper GitHub API
headers (User-Agent, Accept).

Closes #160

Authored-by: Moko Consulting
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

feat: manifest.xml as canonical version source ... e15421699e

- version_bump.php: insert <version> tag into manifest.xml if missing
  (placed before <license> per schema order)
- version_read.php: backfill <version> into manifest.xml from fallback
  sources (README.md, Joomla XML) on first read
- manifest-schema.xsd: add version="09.01.00" attribute to xs:schema
- manifest.xml: add <version>, xsi:schemaLocation pointing to schema
  on moko-platform main branch

Authored-by: Moko Consulting
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

jmiller merged commit fb5461b661 into main 2026-05-26 20:08:03 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

automation

Automated processes or scripts

breaking-change

Breaking API or functionality change

build

Build system changes

ci-cd

CI/CD pipeline changes

config

Configuration file changes

css

CSS/styling changes

dependencies

Dependency updates

deploy-failure

Automated deploy failure tracking

docker

Docker configuration changes

documentation

Documentation changes

dolibarr

Dolibarr module or extension

generic

Generic project or library

good first issue

Good for newcomers

health-check

Repository health check results

health: excellent

Health score 90-100

health: fair

Health score 50-69

health: good

Health score 70-89

health: poor

Health score below 50

help wanted

Extra attention needed

html

HTML template changes

javascript

JavaScript code changes

joomla

Joomla extension or component

mokostandards

MokoStandards compliance

needs-review

Awaiting code review

php

PHP code changes

priority: critical

Critical priority, must be addressed immediately

priority: high

High priority

priority: low

Low priority

priority: medium

Medium priority

push-failure

File push failure requiring attention

python

Python code changes

security

Security-related changes

size/l

Large change (101-300 lines)

size/m

Medium change (31-100 lines)

size/s

Small change (11-30 lines)

size/xl

Extra large change (301-1000 lines)

size/xs

Extra small change (1-10 lines)

size/xxl

Extremely large change (1000+ lines)

standards-drift

Repository drifted from MokoStandards

standards-update

MokoStandards sync update

status: blocked

Blocked by another issue or dependency

status: in-progress

Currently being worked on

status: needs-review

Awaiting code review

status: on-hold

Temporarily on hold

status: pending

Pending action or decision

status: wontfix

This will not be worked on

sync-failure

Bulk sync failure requiring attention

sync-report

Bulk sync run report

template-validation-failure

Template workflow validation failure

tests

Test suite changes

type: bug

Something isn't working

type: chore

Maintenance tasks

type: enhancement

Enhancement to existing feature

type: feature

New feature or request

type: refactor

Code refactoring

type: version

Version-related change

typescript

TypeScript code changes

version

Version bump or release

version-drift

Version mismatch detected

work-in-progress

Work in progress, not ready for merge

bug

Something is not working

chore

Maintenance and housekeeping

documentation

Documentation improvements

enhancement

Improvement to existing functionality

feature

New feature or request

pending: dependency

Blocked by another issue or external dependency

pending: deployment

Tested and approved, awaiting deployment to production

pending: design

Needs UI/UX or architecture design before implementation

pending: documentation

Feature works, needs documentation/wiki update

pending: feedback

Awaiting feedback or decision from stakeholder

pending: review

Implementation complete, awaiting code review

pending: testing

Feature implemented but not yet tested

priority: critical

Must fix immediately

priority: high

Should fix soon

priority: low

Nice to have

priority: medium

Fix when convenient

refactor

Code restructuring without behavior change

roadmap

Planned feature or enhancement tracked on the roadmap

scope: client

Client-specific work

scope: dolibarr

Dolibarr modules and customizations

scope: infrastructure

Server, CI, backups, monitoring

scope: joomla

Joomla templates and extensions

scope: waas

MokoWaaS platform

security

Security vulnerability or hardening

status: blocked

Waiting on external dependency

status: duplicate

Duplicate of another issue

status: in-progress

Being worked on

status: needs-review

Ready for review

status: wontfix

Will not be addressed

No labels

Milestone

No items

No Milestone

Assignees

Clear assignees

jmiller (Jonathan Miller)

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MokoConsulting/moko-platform#168