MokoConsulting/mokoplatform
1
0
Fork 0
Code Issues 9 Pull Requests Releases 8 Wiki Activity

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
Conversation 0 Commits 1 Files Changed 1
+7 -3
jmiller commented 2026-05-26 03:50:20 +00:00
Owner
Copy Link
Copy Source

Automatic cascade

Forward-merging main (81351f4) into dev.

If conflicts exist, resolve manually and merge.

Auto-created by Cascade Main → Dev.

## Automatic cascade Forward-merging `main` (81351f4) into `dev`. If conflicts exist, resolve manually and merge. > Auto-created by **Cascade Main → Dev**.
jmiller added 1 commit 2026-05-26 03:50:21 +00:00
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
81351f45fd 
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>
jmiller merged commit 209dee14fd into dev 2026-05-26 03:50:22 +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
 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
 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
No labels
Priority -
Type -
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/mokoplatform#132
Delete Branch "main"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?