MokoConsulting/MokoSuiteClient
0
0
Fork 0
Code Issues 112 Pull Requests Releases 5 Wiki Activity

fix: sync schema version and add missing license_cache migration #275

Merged
jmiller merged 4 commits from fix/schema-version-sync into main 2026-06-29 15:43:16 +00:00
Conversation 0 Commits 4 Files Changed 44
+64 -53
jmiller commented 2026-06-29 15:16:39 +00:00
Owner
Copy Link
Copy Source

Summary

  • Adds 02.52.00.sql migration file to match the current manifest version
  • Creates the mokosuite_license_cache table that was present in install.mysql.sql but never had a migration file

Problem

Joomla reports a database schema mismatch on sites running MokoSuiteClient:

  • Manifest version: 02.52.00 (or 02.51.08 on suite.dev)
  • Schema version: 02.48.20 (the last SQL update file)

No SQL update files existed between 02.48.20 and 02.52.00, so #__schemas was stuck at the old version. This also caused Joomla to report the issue under MokoSuiteBackup (since MokoSuiteClient is a child package of pkg_mokosuitebackup).

Additionally, the mokosuite_license_cache table was added to install.mysql.sql but never had a migration — so existing installs that upgraded through never received it.

Verified on suite.dev

  • 21 MokoSuiteClient tables exist ✓
  • mokosuite_license_cache is MISSING (confirmed)
  • Schema version stuck at 02.48.20 (confirmed)

Test plan

  • Install updated package on suite.dev
  • Verify mokosuite_license_cache table is created
  • Verify #__schemas for com_mokosuiteclient shows 02.52.00
  • Verify Joomla System → Database no longer shows mismatch
## Summary - Adds `02.52.00.sql` migration file to match the current manifest version - Creates the `mokosuite_license_cache` table that was present in `install.mysql.sql` but never had a migration file ## Problem Joomla reports a database schema mismatch on sites running MokoSuiteClient: - **Manifest version**: 02.52.00 (or 02.51.08 on suite.dev) - **Schema version**: 02.48.20 (the last SQL update file) No SQL update files existed between 02.48.20 and 02.52.00, so `#__schemas` was stuck at the old version. This also caused Joomla to report the issue under **MokoSuiteBackup** (since MokoSuiteClient is a child package of pkg_mokosuitebackup). Additionally, the `mokosuite_license_cache` table was added to `install.mysql.sql` but never had a migration — so existing installs that upgraded through never received it. ## Verified on suite.dev - 21 MokoSuiteClient tables exist ✓ - `mokosuite_license_cache` is **MISSING** (confirmed) - Schema version stuck at `02.48.20` (confirmed) ## Test plan - [ ] Install updated package on suite.dev - [ ] Verify `mokosuite_license_cache` table is created - [ ] Verify `#__schemas` for com_mokosuiteclient shows `02.52.00` - [ ] Verify Joomla System → Database no longer shows mismatch
jmiller added 2 commits 2026-06-29 15:16:40 +00:00
chore(version): pre-release bump to 02.52.02-dev [skip ci]
Universal: Pre-Release / Build Pre-Release (${{ inputs.stability || github.ref_name }}) (push) Successful in 32s
Details
31a049141f
fix: add missing SQL migration for license_cache table and sync schema version
Universal: PR Check / Branch Policy (pull_request) Failing after 3s
Details
Joomla: Extension CI / Release Readiness Check (pull_request) Failing after 7s
Details
Generic: Repo Health / Access control (pull_request) Successful in 3s
Details
Generic: Repo Health / Site Health (pull_request) Has been skipped
Details
Universal: PR Check / Validate PR (pull_request) Failing after 12s
Details
Generic: Project CI / Lint & Validate (pull_request) Successful in 16s
Details
Universal: PR Check / Secret Scan (pull_request) Successful in 21s
Details
Universal: Pre-Release / Build Pre-Release (${{ inputs.stability || github.ref_name }}) (push) Successful in 30s
Details
Joomla: Extension CI / Lint & Validate (pull_request) Failing after 1m2s
Details
Joomla: Metadata Validation / Validate Joomla Metadata (pull_request) Successful in 1m3s
Details
Universal: Build & Release / Promote to RC (pull_request) Failing after 13s
Details
Universal: Build & Release / Build & Release Pipeline (pull_request) Has been skipped
Details
Generic: Project CI / Tests (pull_request) Has been cancelled
Details
Joomla: Extension CI / Tests (PHP 8.2) (pull_request) Has been cancelled
Details
Joomla: Extension CI / Tests (PHP 8.3) (pull_request) Has been cancelled
Details
Joomla: Extension CI / PHPStan Analysis (pull_request) Has been cancelled
Details
Joomla: Extension CI / Build RC Pre-Release (pull_request) Has been cancelled
Details
Universal: PR Check / Build RC Package (pull_request) Has been cancelled
Details
Universal: PR Check / Report Issues (pull_request) Has been cancelled
Details
Generic: Repo Health / Scripts governance (pull_request) Has been cancelled
Details
Generic: Repo Health / Repository health (pull_request) Has been cancelled
Details
Generic: Repo Health / Report: Scripts Governance (pull_request) Has been cancelled
Details
Generic: Repo Health / Report: Repository Health (pull_request) Has been cancelled
Details
e746afd835 
The mokosuite_license_cache table was added to install.mysql.sql but
never had a corresponding update file. Existing installs (upgrading
from pre-02.48.20) never received this table.

Additionally, no SQL update files existed between 02.48.20 and 02.52.00,
causing Joomla to report a database schema mismatch (manifest says
02.52.00 but #__schemas is stuck at 02.48.20).
jmiller added 1 commit 2026-06-29 15:16:59 +00:00
chore(version): pre-release bump to 02.52.03-dev [skip ci] 54e61ded92
jmiller added 1 commit 2026-06-29 15:17:31 +00:00
chore(version): pre-release bump to 02.52.04-dev [skip ci]
Universal: Build & Release / Promote to RC (pull_request) Has been skipped
Details
RC Revert / Rename rc/ back to dev/ (pull_request) Has been skipped
Details
Branch Cleanup / Delete merged branch (pull_request) Successful in 2s
Details
Universal: Build & Release / Build & Release Pipeline (pull_request) Successful in 35s
Details
Universal: Workflow Sync Trigger / Sync workflows to live repos (pull_request) Successful in 4m21s
Details
dea991a3b2
jmiller merged commit 8e564b1fca into main 2026-06-29 15:43:16 +00:00
jmiller deleted branch fix/schema-version-sync 2026-06-29 15:43:17 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
architecture
automation
Automated processes or scripts
 breaking-change
Breaking API or functionality change
 bug
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
 duplicate
enhancement
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
 invalid
javascript
JavaScript code changes
 joomla
Joomla extension or component
 major-release
Major version release (breaking changes)
 minor-release
Minor version release (XX.YY.00)
 mokostandards
MokoStandards compliance
 needs-review
Awaiting code review
 needs-testing
Requires manual or automated testing
 patch-release
Patch version release (XX.YY.ZZ)
 php
PHP code changes
 priority: critical
priority: high
priority: low
priority: medium
push-failure
File push failure requiring attention
 python
Python code changes
 question
regression
Regression from a previous working state
 release-candidate
Release candidate build
 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
 standards-violation
Standards compliance failure
 status: blocked
status: in-progress
status: needs-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
 test-failure
Automated test 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: release
Release preparation or tracking
 type: test
Test suite additions or changes
 type: version
Version-related change
 typescript
TypeScript code changes
 version
Version bump or release
 version-branch
Version branch related
 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/MokoSuiteClient#275
Delete Branch "fix/schema-version-sync"

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?