chore(sync): cascade main -> dev #340
Open
jmiller
wants to merge 197 commits from
main into dev
pull from: main
merge into: :dev
:main
:chore/template-client-name
:chore/client-mokosuite-prefix
:chore/normalize-docs
:dev
:version/09.43.00
:fix/submodule-release-download
:feature/321-version-bump-scripts-perpetuate-duplicat
:feature/304-release-publish
:fix/namespace-cleanup
:rc
No Reviewers
Labels
Clear labels
automation
breaking-change
build
ci-cd
config
css
dependencies
deploy-failure
docker
documentation
dolibarr
generic
good first issue
health-check
health: excellent
health: fair
health: good
health: poor
help wanted
html
javascript
joomla
mokostandards
needs-review
php
push-failure
python
security
size/l
size/m
size/s
size/xl
size/xs
size/xxl
standards-drift
standards-update
sync-failure
sync-report
template-validation-failure
tests
type: bug
type: chore
type: enhancement
type: feature
type: refactor
type: version
typescript
version
version-drift
work-in-progress
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Automated processes or scripts
Breaking API or functionality change
Build system changes
CI/CD pipeline changes
Configuration file changes
CSS/styling changes
Dependency updates
Automated deploy failure tracking
Docker configuration changes
Documentation changes
Dolibarr module or extension
Generic project or library
Good for newcomers
Repository health check results
Health score 90-100
Health score 50-69
Health score 70-89
Health score below 50
Extra attention needed
HTML template changes
JavaScript code changes
Joomla extension or component
MokoStandards compliance
Awaiting code review
PHP code changes
File push failure requiring attention
Python code changes
Security-related changes
Large change (101-300 lines)
Medium change (31-100 lines)
Small change (11-30 lines)
Extra large change (301-1000 lines)
Extra small change (1-10 lines)
Extremely large change (1000+ lines)
Repository drifted from MokoStandards
MokoStandards sync update
Bulk sync failure requiring attention
Bulk sync run report
Template workflow validation failure
Test suite changes
Something isn't working
Maintenance tasks
Enhancement to existing feature
New feature or request
Code refactoring
Version-related change
TypeScript code changes
Version bump or release
Version mismatch detected
Work in progress, not ready for merge
Something is not working
This issue or pull request already exists
New feature
Need some help
Something is wrong
More information is needed
This won't be fixed
No labels
Priority
-
Type
-
Milestone
No items
No Milestone
Assignees
jmiller (Jonathan Miller)
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: MokoConsulting/MokoCLI#340
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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?
Automated cascade of main into dev. Auto-merges only if conflict-free; otherwise left open for manual resolution.
- Fix if: condition syntax (needs ${{ }} expression wrapper) - Point Packagist notification to GitHub mirror URL (Packagist can't access Gitea directly)Untrusted ${{ }} expressions (issue titles, PR head refs, reusable-workflow inputs) were interpolated directly into run: shell bodies, allowing command injection. Each is now passed through an env: block and referenced as a shell variable in the script (env vars are not subject to ${{ }} expansion). Files: - ci-issue-reporter.yml inputs.gate/details/severity/workflow - issue-branch.yml github.event.issue.title - branch-cleanup.yml github.event.pull_request.head.ref - pr-check.yml github.head_ref / github.base_ref - auto-release.yml github.event.pull_request.head.ref (x2) Propagates to all template consumers via the workflow sync. Refs MokoConsulting/Template-Joomla#35. Authored-by: Moko Consultingbranch_rename.php deleted the target branch then recreated it. When the target (rc) is a protected branch, the delete silently fails and the recreate returns HTTP 409 'branch already exists', breaking every PR-to-main promote-rc. Force-update the ref in place via PATCH git/refs/heads/{to} (sha+force) when the target exists; still create it when it doesn't. Requires the CI token to have force-push permission on the protected rc branch.The repo was renamed mokoplatform -> mokocli; this rewrites every stale reference across the tree (case-sensitive): MokoPlatform -> MokoCLI (DEFGROUP/INGROUP doc tags) mokoplatform -> mokocli (repo URLs, /opt & /tmp paths, clone URLs, EXCLUDE lists, XML xmlns + <root> namespace) moko-platform -> moko-cli (marker files) XML namespace URIs and ManifestParser::NAMESPACE_URI are changed in lockstep so local manifest-vs-parser validation stays consistent. The external standards.mokoconsulting.tech namespace endpoint must be updated to match separately (tracked in #336). Refs #336 Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2iView command line instructions
Checkout
From your project repository, check out a new branch and test the changes.