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

fix: auto-release Step 8 uses joomla_build.php — not universal #173

New Issue
Closed
opened 2026-05-26 21:16:14 +00:00 by jmiller · 1 comment
jmiller commented 2026-05-26 21:16:14 +00:00
Owner
Copy Link
Copy Source

Problem

auto-release.yml Step 8 calls joomla_build.php which is Joomla-specific. Non-Joomla repos (Dolibarr, generic, MCP) either fail or skip packaging entirely.

Solution

Replace with release_package.php which already handles all platforms via manifest.xml detection.

Files

  • .mokogitea/workflows/auto-release.yml (Step 8)
## Problem auto-release.yml Step 8 calls `joomla_build.php` which is Joomla-specific. Non-Joomla repos (Dolibarr, generic, MCP) either fail or skip packaging entirely. ## Solution Replace with `release_package.php` which already handles all platforms via manifest.xml detection. ## Files - .mokogitea/workflows/auto-release.yml (Step 8)
jmiller added the ci-cdbuild labels 2026-05-26 21:16:14 +00:00
jmiller commented 2026-05-26 21:16:16 +00:00
Author
Owner
Copy Link
Copy Source

Branch created: feature/173-fix-auto-release-step-8-uses-joomla-buil

git fetch origin
git checkout feature/173-fix-auto-release-step-8-uses-joomla-buil
Branch created: [`feature/173-fix-auto-release-step-8-uses-joomla-buil`](https://git.mokoconsulting.tech/MokoConsulting/moko-platform/src/branch/feature/173-fix-auto-release-step-8-uses-joomla-buil) ```bash git fetch origin git checkout feature/173-fix-auto-release-step-8-uses-joomla-buil ```
Sign in to join this conversation.
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 build ci-cd
Priority -
Type Bug
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#173
Delete Branch "%!s()"

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?