Skip to content

Close frontend and Marketplace compatibility gaps - #37

Merged
lucamykael merged 2 commits into
mainfrom
codex/close-explicit-compatibility-gaps
Aug 4, 2026
Merged

Close frontend and Marketplace compatibility gaps#37
lucamykael merged 2 commits into
mainfrom
codex/close-explicit-compatibility-gaps

Conversation

@lucamykael

Copy link
Copy Markdown
Owner

Summary

  • close the remaining Mendix 10/11 native frontend compatibility gaps
  • add fail-closed frontend schema/layout/design-property migration and reproducible acceptance gates
  • add official Marketplace dependency resolution, transactional update/remove, widget installation, and protocol planning
  • preserve assets, package originals, lock/cache provenance, native structures, and version-specific compiler seeds
  • expose MxBuild zero-error validation and observable mx check diagnostics for source/rebuild

Validation

  • 1,002 examples, 0 failures
  • 100.00% lines (16,917/16,917)
  • 100.00% branches (6,659/6,659)
  • RuboCop: 238 files, 0 offenses
  • git diff --check: clean
  • Mendix 10.24.0.73019: source/rebuild frontend_ready, 0 MxBuild errors
  • Mendix 11.12.1: source/rebuild frontend_ready, 0 MxBuild errors
  • mx check source/rebuild signatures are identical:
    • 10.24: 0 errors, 173 package-owned warnings, 0 deprecations, 2 best-practice recommendations
    • 11.12: 0 errors, 10 package-owned warnings, 0 deprecations, 2 best-practice recommendations

The observable warnings belong to locked Marketplace modules; the round trip preserves them exactly and introduces no application-owned diagnostic drift.

@lucamykael
lucamykael merged commit 0b0a349 into main Aug 4, 2026
3 checks passed
@lucamykael
lucamykael deleted the codex/close-explicit-compatibility-gaps branch August 4, 2026 20:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant