MokoConsulting/Template-Joomla
Template
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(workflows): Universal auto-release with .moko-platform detection #3

Closed
jmiller wants to merge 0 commits from dev into main
pull from: dev
merge into: :main
Conversation 0 Commits - Files Changed -
jmiller commented 2026-05-12 03:21:36 +00:00
Owner
Copy Link
Copy Source

Summary

  • Replace platform-specific auto-release with Universal: Build & Release
  • Add .moko-platform file for platform detection
  • Smart case/esac branching for joomla|dolibarr|generic platforms
  • Dolibarr post-release: reset dev version to 'development'
  • Rename workflows with Universal:/Platform: prefixes

Test plan

  • Verify .moko-platform content is correct per repo
  • Trigger workflow_dispatch to test platform detection
  • Confirm Gitea Actions UI shows correct prefixed names
## Summary - Replace platform-specific auto-release with **Universal: Build & Release** - Add `.moko-platform` file for platform detection - Smart `case/esac` branching for joomla|dolibarr|generic platforms - Dolibarr post-release: reset dev version to 'development' - Rename workflows with Universal:/Platform: prefixes ## Test plan - [ ] Verify .moko-platform content is correct per repo - [ ] Trigger workflow_dispatch to test platform detection - [ ] Confirm Gitea Actions UI shows correct prefixed names
jmiller self-assigned this 2026-05-12 03:21:36 +00:00
jmiller added 3 commits 2026-05-12 03:21:36 +00:00
Merge pull request 'chore: cascade main → dev (f4b600d) [skip ci]' (#2) from main into dev fb84c76a84
chore: sync auto-release.yml from MokoGalleryCalendar [skip ci] 06c6ebb2b7
feat(workflows): Universal auto-release with .moko-platform detection
Joomla: Repo Health / Access control (push) Successful in 1s
Details
Joomla: Repo Health / Release configuration (push) Failing after 3s
Details
Joomla: Repo Health / Scripts governance (push) Successful in 3s
Details
Joomla: Repo Health / Repository health (push) Failing after 3s
Details
Joomla: Extension CI / Release Readiness Check (pull_request) Failing after 3s
Details
Joomla: Extension CI / Lint & Validate (pull_request) Failing after 4s
Details
Universal: Branch Policy Check / Verify merge target (pull_request) Successful in 1s
Details
Joomla: Extension CI / Tests (PHP 8.2) (pull_request) Has been skipped
Details
Joomla: Extension CI / Tests (PHP 8.3) (pull_request) Has been skipped
Details
Joomla: Extension CI / PHPStan Analysis (pull_request) Has been skipped
Details
Universal: Secret Scanning / Gitleaks Secret Scan (pull_request) Successful in 3s
Details
Universal: PR Check / Validate PR (pull_request) Successful in 3s
Details
Joomla: Repo Health / Access control (pull_request) Successful in 1s
Details
Joomla: Repo Health / Release configuration (pull_request) Failing after 3s
Details
Joomla: Repo Health / Scripts governance (pull_request) Successful in 2s
Details
Joomla: Repo Health / Repository health (pull_request) Failing after 3s
Details
f8a3028f0f 
- Replace Joomla-specific auto-release with Universal: Build & Release
- Add .moko-platform file (joomla) for platform detection
- Rename all workflows with Universal:/Joomla: prefixes
- Smart case/esac branching for joomla|dolibarr|generic platforms
- Add Dolibarr post-release version reset support

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
jmiller closed this pull request 2026-05-12 03:33:30 +00:00

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
breaking-change
Breaking API or behavior change
 ci-cd
CI/CD pipeline changes
 config
Configuration changes
 css
CSS/styling changes
 dependencies
Dependency updates
 deploy-failure
Deployment failed
 documentation
Documentation changes
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 html
HTML/template changes
 joomla
Joomla extension
 major-release
Major version release
 minor-release
Minor version release
 mokostandards
Related to MokoStandards framework
 patch-release
Patch version release
 php
PHP code
 priority: critical
Must fix immediately
 priority: high
Important, fix soon
 priority: low
Nice to have
 priority: medium
Normal priority
 push-failure
Git push operation failed
 release-candidate
Release candidate build
 security
Security vulnerability or hardening
 size/l
200-500 lines changed
 size/m
50-200 lines changed
 size/s
10-50 lines changed
 size/xl
500+ lines changed
 size/xs
< 10 lines changed
 standards-drift
Deviates from MokoStandards
 standards-update
MokoStandards compliance update
 status: blocked
Blocked by dependency or decision
 status: in-progress
Actively being worked on
 status: needs-review
Awaiting code review
 status: on-hold
Paused intentionally
 status: wontfix
Will not be addressed
 sync-failure
Sync or mirror failed
 type: bug
Something isn't working
 type: chore
Maintenance, dependencies, cleanup
 type: enhancement
Improvement to existing feature
 type: feature
New functionality
 type: refactor
Code restructuring without behavior change
 type: version
Version bump or release
 version-drift
Version mismatch across files
 work-in-progress
Draft or incomplete work
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
Projects
Clear projects
No projects
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees jmiller
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/Template-Joomla#3
Delete Branch "dev"

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?