Mage-OS February Update
· mage-os-team · Updates · 3 min read
February was an active month for Mage-OS, with important progress in development, testing, infrastructure, and community collaboration.
New Release Manager
Please welcome Marcel Martinez as our new Release Manager. Marcel will coordinate releases, improve processes, and help ensure stability and consistency across future Mage-OS versions. This is an important step toward a more structured and predictable release cycle.
New Website
A new Mage-OS website went live. It is based on a static site generator and replaces the previous WordPress setup. The repository is public, and content can be edited directly via GitHub, supporting transparency and easier community contributions.
2nd Mage-OS Hackathon
On 13 February, we held our second Mage-OS Hackathon. Community members collaborated on several initiatives:
- Extension of the Mage-Check GitHub Action, including Mage-OS support and potential integration of PHPStan and additional static analysis tools.
- Work on Playwright testing and CI integration.
- Progress on a JavaScript optimizer and RequireJS-related improvements.
- Development of an open source RMA (Return Merchandise Authorization) module, providing built-in return management functionality for merchants.
- Initial ideas for a simplified Mage-OS installer that can auto-detect environments such as DDEV or Warden and guide users through setup.
The hackathon showed strong collaboration and delivered practical improvements to the ecosystem.
Playwright Testing Progress
Significant work was done on integrating Playwright end-to-end tests into Mage-OS.
- Around two-thirds of the existing Elgentos Playwright test suite are currently passing.
- A CI workflow was prepared to execute Playwright tests directly within the Mage-OS repository.
- Key challenges include differences between Mage-OS and Adobe Commerce (especially in the Admin UI), as well as dependencies on themes, sample data, and checkout implementations.
- It was discussed that a fork or Mage-OS–specific adaptation of the test suite is likely necessary.
- An alternative modular Playwright architecture was introduced, separating base tests, theme tests, and checkout tests, and supporting multiple locales and checkout variations.
The goal is to achieve reliable end-to-end coverage that fits Mage-OS requirements.
Development Environment Improvements
A new GitHub Codespaces based development container was presented. The goal is to simplify local development and reduce setup friction.
Key characteristics:
- Support for multiple Magento versions.
- Alpine-based images with daily builds.
- Preconfigured tools such as Xdebug and common developer utilities.
- VS Code integration.
- Designed as a maintainable alternative to older Docker-based setups.
This approach aims to standardize development environments and lower the entry barrier for contributors.
Design System Update
The Mage-OS design system was updated to version 1.1.0. The UI now aligns more closely with Google Material guidelines, with improved consistency in layout, spacing, and interaction behavior. Several component-level refinements were introduced to improve visual alignment and usability.
Powered by Strong Partnerships
We are proud to collaborate with industry leaders who believe in open source and help accelerate the Mage-OS ecosystem.
Gold Partners
Silver Partners
Bronze Partners
Why Partner With Us?
Becoming a Mage-OS partner means more than visibility. It means shaping the future of open source commerce, gaining early insights into technical developments, and showcasing your brand to a global audience of merchants, developers, and agencies.
