Mage-OS Updates

Mage-OS 2.0: Innovation Takes Flight

fabrizio-balliano — Thu, 16 Oct 2025 00:00:00 GMT

We are excited to announce the release of Mage-OS Distribution 2.0, a major milestone that shows the power of community-driven innovation. This release represents a significant step forward in Mage-OS’s commitment to advancing open-source e-commerce.

Our Foundation

Mage-OS 2.0 builds on Magento Open Source 2.4.8-p3, including all the latest security fixes and platform improvements from the upstream release. This ensures that our distribution maintains the solid foundation that hundreds of thousands of developers and merchants worldwide depend on, while adding the improvements that make Mage-OS special.

See recommended software versions

Component	Recommended Version
Composer	2.8
OpenSearch	2.19
MariaDB	11.4
MySQL	8.4
PHP	8.4/8.3
RabbitMQ	4
Redis	Valkey 8 (or Redis 7.2+)
Varnish	7.6
Apache	2.4
nginx	1.26

Version and Support Policy

We adopted a new versioning policy, starting with Mage-OS 1.2 in June. This is our first major update.

#.0.0 Major Updates
- 2x per year, around April/May and October.
- These may include new features, useful bundled extensions, significant changes, or changes to system requirements like PHP versions.
- They should stay mostly compatible with Magento and existing extensions, allowing you to easily switch between Mage-OS and Magento.
2.#.0 Minor Updates
- Any Magento release or security patch between a feature release will become a Mage-OS minor version update, unless there is a change in system requirements.
- These should be compatible with existing installations.
2.0.# Patch Updates
- Small but critical off-schedule fixes to a Mage-OS release. These should be rare.

This reflects our plan for more rapid releases and innovation, and lets everyone know and plan for updates in advance.

Adobe announced plans to release security patches on the second Tuesday of each month in 2026. Mage-OS will publish an update each time with the latest security patches included.

As a mostly-volunteer-run nonprofit, our resources are limited. As such, for now, Mage-OS will only support the latest release branch at a time. You must stay up to date with the latest Mage-OS release to stay secure.

The Mage-OS Lab: Where Innovation Develops

One of the most exciting aspects of Mage-OS 2.0 is that we’ve graduated multiple Mage-OS Lab modules into the core distribution. The Mage-OS Lab is our innovation space, where we welcome everyone in the community to experiment, improve, and perfect new ideas and improvements for the Magento ecosystem.

The Lab represents our future of open-source Magento: collaborative, experimental, and community-driven. It’s where new ideas are tested, improved, and ultimately brought to life for the benefit of the entire ecosystem.

These modules represent months of dedicated work by talented developers who believe in pushing the platform forward.

New Features

Enhanced Security with PCI DSS 4.0 Compliance

Mage-OS 2.0 bundles the aligent/magento2-pci-4-compatibility module, which updates default admin policies for PCI DSS 4.0 requirements. This includes:

Automatic account deactivation after 90 days of inactivity
Enhanced session security with 15-minute idle timeout enforcement
Strengthened authentication with improved lockout policies
More strict password requirements with 12-character minimum length and complexity rules

AI-Powered Automatic Translation

The Automatic Translation module changes how merchants expand globally. This powerful tool uses AI services from DeepL, OpenAI, or Google Gemini to provide:

Product catalog translation with support for both text and select/multiselect attributes
Automated cron-based translation workflows for hands-off operation
Manual translation controls for categories, CMS pages, and static blocks
Intelligent retranslation prevention that respects manual edits while adapting to source changes

Use of AI translation requires a separate AI service account and API key, and will involve costs by usage.

Advanced Inventory Management

The new Inventory Reservations Grid brings better visibility to your inventory management, allowing you to directly see and manage stock reservations in Magento’s inventory system.

SEO Tuning Made Simple

The Meta Robots Tag module gives you detailed control over search engine indexing. With three new attributes in the “Search Engine Optimization” section of products, categories, and CMS pages, you can fine-tune your NOINDEX, NOFOLLOW, and NOARCHIVE tags page by page.

Page Builder Enhancements

Two powerful Page Builder enhancements from Mage-OS Lab are now part of Mage-OS 2:

Embedded Widgets

Page Builder Widgets adds “CMS Widget” support directly into Page Builder, including previews of the widget output. This can be used anywhere Page Builder is supported, including pages, blocks, and content descriptions.

Import/Export and Remote Sync

PageBuilder Template Import/Export enables Page Builder templates to be easily shared between Magento instances. This module supports both local file transfers and cloud-based Dropbox integration for template management workflows across multiple websites or instances.

Performance Optimization

The Theme Optimization module delivers better user experience based on the latest browser features:

Back/Forward Cache (bfcache) support gives almost instant browser navigation backwards/forwards on cacheable pages
Speculative preloading intelligently preloads links before the user clicks them
Smooth page transitions create a premium user experience

All of these combine to give a smoother experience and better Core Web Vitals than without.

Core Platform Improvements

Beyond the new modules, Mage-OS 2.0 includes several important platform improvements developed by our community:

GitHub Pull Request Contributions

Several key contributions from the community have been integrated:

Admin Dashboard JavaScript Fix (#164): Ryan Hoerr resolved a JavaScript error that could occur on admin login.
Config Load Safety Check (#167): ProxiBlue added a config safety check to better handle missing config id values.
Configurable Product Export Fix (#169): Ryan Hoerr fixed product export issues for configurable products with multiple super attributes.
PHP 8.4 Compatibility (#157): aelmizeb fixed PHP 8.4 deprecation errors on compilation.
USPS API Migration (#170): We added Magento patch AC-15210 for support of the USPS REST API. USPS will be turning off the legacy Web Services API on January 26, 2026.

Celebrating Our Community

Mage-OS wouldn’t exist without the support of our growing community. We extend our thanks to our 172 financial contributors who have collectively contributed over €106,000 to fund this mission since 2022. This has gotten us where we are today, but every bit more will help us to do more faster. Please add your support and help us do something great!

Our Partner Ecosystem

Gold Partners (€10,000/year):

MDOQ - Leading the way with €20,000 in total contributions
Interactiv4 - Our first Gold Partner with €10,000 contributed

Silver Partners (€4,000/year):

ParadoxLabs
Hyvä Themes
Vendic
Inchoo
Mollie
WilMa Digital

Bronze Partners (€1,250/year):

JetRails, Develo, FindCanary, JH, integer_net, and basecom

We also celebrate our 81 Community Members and 67 Professional Members who power the grassroots support that makes everything possible.

Special Recognition

Thank you to the people who made Mage-OS 2.0 possible:

Davide Lunardon, Luca Fuser, and Samuele Martini for the Automatic Translation and PageBuilder modules
Ryan Hoerr, Oliver Jaufmann/JaJuMa GmbH, Sean van Zuidam, and David Lambauer for the Theme Optimization module
The Aligent team for their PCI 4.0 Compatibility module
Ryan Hoerr and Fabrizio Balliano for multiple platform fixes and release management
ProxiBlue and aelmizeb for their platform improvements

And to the many more that participated, tested, commented, worked in Mage-OS Lab, or otherwise supported our efforts.

Join the Community

Do you want to be part of the future of e-commerce?

The success of Mage-OS depends on community support and involvement. Whether you’re a developer, merchant, agency, or technology partner, we need you.

For Individuals

Community Member: €10/year - Show your support and get voting rights
Professional Member: €100/year - For those making a living with the platform

For Businesses

Bronze Partner: €1,250/year - Perfect for small companies
Silver Partner: €4,000/year - Includes logo placement on Mage-OS.org
Gold Partner: €10,000/year - Premium visibility and partnership benefits
Platinum Partner: €25,000/year - Be the first! Maximum impact and recognition

Become a sponsor today: mage-os.org/about/mage-os-membership

Get Involved in Development

Join our weekly tech meetings every Tuesday at 3 PM CET on Discord. Contribute to the Mage-OS Lab, submit pull requests, or share your ideas with the community.

Repository: github.com/mage-os/mageos-magento2
Lab Projects: github.com/mage-os-lab
Community Chat: chat.mage-os.org

If you have an Open Source module you are interested in including or contributing, get in touch!

Installing Mage-OS 2.0

Ready to experience the future? Create a new Mage-OS project with:

composer create-project --repository-url=https://repo.mage-os.org/ mage-os/project-community-edition .

Upgrading from Magento

You can convert from Magento to Mage-OS with one line (sort of):

composer config repositories.0 composer https://repo.mage-os.org/ &&
composer require mage-os/product-community-edition --no-update &&
composer remove magento/product-community-edition magento/composer-dependency-version-audit-plugin magento/composer-root-update-plugin --no-update &&
composer update --no-plugins --with-all-dependencies

We recommend updating to the latest available Magento version before switching to Mage-OS, to make the process as smooth as possible.

The Future

Mage-OS 2.0 represents more than just a software release, it’s proof that community-driven innovation works. Every module that graduated from the Lab, every security enhancement, and every performance improvement exists because dedicated developers and forward-thinking businesses chose to invest in the future of open-source e-commerce.

This is just the beginning. With your support, Mage-OS will continue to evolve, innovate, and lead the way toward a more accessible, powerful, and community-controlled e-commerce future.

Welcome to Mage-OS 2.0. Welcome to the future of e-commerce.

For complete installation instructions and technical details, visit devdocs.mage-os.org. Join our community discussions on Discord, and follow our progress on GitHub.

Mage-OS 1.3.1: Important security update

fabrizio-balliano — Tue, 09 Sep 2025 00:00:00 GMT

We are excited to announce the release of Mage-OS Distribution 1.3.1, another step in the building of the definitive open source e-commerce platform!

Mage-OS 1.3.1 is built on Magento Open Source 2.4.8-p2, and includes an important security update from Magento Open Source that was released just this morning.

This update fixes vulnerability CVE-2025-54236, by applying the official Adobe security patch to Mage-OS. There are no other changes from Mage-OS 1.3.0.

Security Bulletin: APSB25-88
Magento Security Patch: Action Required: Critical Security Update Available for Adobe Commerce  (APSB25-88)

Please update any Mage-OS instances to version 1.3.1 as soon as possible to prevent security issues.

composer require mage-os/product-community-edition:1.3.1
bin/magento setup:upgrade

If you have Magento or Adobe Commerce, you will need to apply the Adobe security patch available through the link above.

Want to participate?

Are you interested in contributing to Mage-OS, or have a bug or improvement you’d like to make? We welcome pull requests at https://github.com/mage-os/mageos-magento2!

If you have a bigger project in mind, please join Discord and chat about your idea. We’d be delighted to hear from you, and help figure out how your idea best fits into Mage-OS!

Installing Mage-OS

You can create a new Mage-OS project with the following SSH command:

composer create-project --repository-url=https://repo.mage-os.org/ mage-os/project-community-edition .

After a successful composer download, you will need to run the installer. Please see DevDocs: Installation Guide for Mage-OS

Moving to Mage-OS

If you are already using Magento 2.4 and PHP 8.2+, you can change to Mage-OS by running the following in SSH:

composer config repositories.0 composer https://repo.mage-os.org/ && 
    composer require mage-os/product-community-edition --no-update && 
    composer remove magento/product-community-edition magento/composer-dependency-version-audit-plugin magento/composer-root-update-plugin --no-update && 
    composer remove sebastian/comparator --dev --no-update && 
    composer update --no-plugins --with-all-dependencies

We strongly recommend updating to the latest Magento version (currently 2.4.8) before changing to Mage-OS, to minimize issues.

Your specific situation may require additional changes to your composer.json file. Generally this will involve changing magento/ package names to mage-os/, or updating dependency versions.

Mage-OS 1.3.0 is out now!

fabrizio-balliano — Fri, 15 Aug 2025 00:00:00 GMT

We are excited to announce the release of Mage-OS Distribution 1.3.0, another step in the building of the definitive open source e-commerce platform!

Our foundation

Mage-OS 1.3.0 is built on Magento Open Source 2.4.8-p2, and includes all platform updates and community fixes from the upstream release. See the full Magento Open Source 2.4.8-p2 Release Notes for details.

The latest recommended software versions are:

Composer	2.8
Elasticsearch	— (no longer supported)
OpenSearch	2.19
MariaDB	11.4
MySQL	8.4
PHP	8.4/8.3
RabbitMQ	4
Redis	Valkey 8 (or Redis 7.2+)
Varnish	7.6
Apache	2.4
nginx	1.26

Updates to our backend theme

In this release, we enhanced the user interface with improved icon styling, refined newsletter and email template views, optimized data grids and modals, updated jstree components and media galleries, refactored URL rewrites, and fixed LESS configuration issues for greater usability.

Other updates

Fixed JavaScript error encountered when selecting “All Resources” by Lucas van Staden
Fixed integration tests for Magento_Backend and Magento_Bundle by Simon Humeau (Antadis)
Fixed missing screen-l styles added using .media-width mixin by Vova Yatsyuk
Fixed city name validation to allow digits, &, ., () characters by Bhushan Kumar

Thanks to everyone that helped with this release!

Mage-OS wouldn’t exist without a great community. ❤️ Among others, thank you to:

Artem Kozynets
Bhushan Kumar
Fabrizio Balliano
Lucas van Staden
Ryan Hoerr
Simon Humeau (Antadis)
Vinai Kopp
Vova Yatsyuk

And to everyone that has helped with testing, feedback, and our weekly tech meetings!

Want to participate?

Are you interested in contributing to Mage-OS, or have a bug or improvement you’d like to make? We welcome pull requests at https://github.com/mage-os/mageos-magento2!

If you have a bigger project in mind, please join Discord and chat about your idea. We’d be delighted to hear from you, and help figure out how your idea best fits into Mage-OS!

Installing Mage-OS

You can create a new Mage-OS project with the following SSH command:

composer create-project --repository-url=https://repo.mage-os.org/ mage-os/project-community-edition .

After a successful composer download, you will need to run the installer. Please see DevDocs: Installation Guide for Mage-OS

Moving to Mage-OS

If you are already using Magento 2.4 and PHP 8.2+, you can change to Mage-OS by running the following in SSH:

composer config repositories.0 composer https://repo.mage-os.org/ && 
    composer require mage-os/product-community-edition --no-update && 
    composer remove magento/product-community-edition magento/composer-dependency-version-audit-plugin magento/composer-root-update-plugin --no-update && 
    composer remove sebastian/comparator --dev --no-update && 
    composer update --no-plugins --with-all-dependencies

We strongly recommend updating to the latest Magento version (currently 2.4.8) before changing to Mage-OS, to minimize issues.

Your specific situation may require additional changes to your composer.json file. Generally this will involve changing magento/ package names to mage-os/, or updating dependency versions.

Mage-OS 1.2.0 is out now!

fabrizio-balliano — Wed, 18 Jun 2025 00:00:00 GMT

We are excited to announce the release of Mage-OS Distribution 1.2.0, another step in the building of the definitive open source e-commerce platform!

Our foundation

Mage-OS 1.2.0 is built on Magento Open Source 2.4.8-p1, and includes all platform updates and community fixes from the upstream release. See the full Magento Open Source 2.4.8-p1 Release Notes for details.

The latest recommended software versions are:

Composer	2.8
Elasticsearch	— (no longer supported)
OpenSearch	2.19
MariaDB	11.4
MySQL	8.4
PHP	8.4/8.3
RabbitMQ	4
Redis	Valkey 8 (or Redis 7.2+)
Varnish	7.6
Apache	2.4
nginx	1.26

Updates to our backend theme

In this release, we’ve improved the user experience by fixing username clipping, introducing smooth view transitions, preventing layout jumps with a new scrollbar-gutter, adjusting footer copyright spacing, and resolving an issue where media search overlapped the upload image message.

Thanks to everyone that helped with this release!

Mage-OS wouldn’t exist without a great community. ❤️ Among others, thank you to:

Artem Kozynets
Damien Retzinger
Fabrizio Balliano
Ryan Hoerr
Sean van Zuidam
Vinai Kopp

Along with recent Mage-OS Lab contributors:

Davide Lunardon
Luca Fuser
Ryan Sun
Samuele Martini
Stefano Tusino

And to everyone that has helped with testing, feedback, and our weekly tech meetings!

Want to participate?

Are you interested in contributing to Mage-OS, or have a bug or improvement you’d like to make? We welcome pull requests at https://github.com/mage-os/mageos-magento2!

If you have a bigger project in mind, please join Discord and chat about your idea. We’d be delighted to hear from you, and help figure out how your idea best fits into Mage-OS!

Installing Mage-OS

You can create a new Mage-OS project with the following SSH command:

composer create-project --repository-url=https://repo.mage-os.org/ mage-os/project-community-edition .

After a successful composer download, you will need to run the installer. Please see DevDocs: Installation Guide for Mage-OS

Moving to Mage-OS

If you are already using Magento 2.4 and PHP 8.2+, you can change to Mage-OS by running the following in SSH:

composer config repositories.0 composer https://repo.mage-os.org/ && 
    composer require mage-os/product-community-edition --no-update && 
    composer remove magento/product-community-edition magento/composer-dependency-version-audit-plugin magento/composer-root-update-plugin --no-update && 
    composer remove sebastian/comparator --dev --no-update && 
    composer update --no-plugins --with-all-dependencies

We strongly recommend updating to the latest Magento version (currently 2.4.8) before changing to Mage-OS, to minimize issues.

Your specific situation may require additional changes to your composer.json file. Generally this will involve changing magento/ package names to mage-os/, or updating dependency versions.

Hyvä Developers Paradise 2025: The Power of Community Driving Magento’s Future

ruggero-landolina — Wed, 21 May 2025 00:00:00 GMT

Article by Ruggero Landolina

From February 27 to March 1, 2025, the first-ever Hyvä Developers Paradise took place at the Lopesan Baobab Resort in Las Palmas de Gran Canaria. This remarkable event was dedicated to Magento developers and eCommerce professionals. But this was more than just a technical conference. It was a gathering of like-minded individuals, celebrating community, collaboration, and shared purpose.

New milestones for the Hyvä ecosystem were unveiled during the event, including Hyvä Commerce—a suite of products enhancing Magento Open Source with a modern admin panel and advanced features—and Hyvä CMS, a fully redesigned content management system built for flexibility and usability. These innovations are a testament to the fact that, with strong community support, Magento remains one of the most powerful and adaptable eCommerce platforms.

A Community at the Center: Unity Through Collaboration

One of the clearest takeaways from these action-packed days was a renewed awareness: Magento still holds a vital place in the eCommerce world, but maintaining that position requires collective effort. The presence of Mage-OS and the Magento Association as community sponsors underscored the importance of joining forces to strengthen and evolve the Magento ecosystem.

Many Mage-OS contributors were present, openly discussing what it would take to bring Magento back to the market position it deserves. One message was clear: collaboration is the only path forward—between developers, agencies, vendors, and professionals across the industry.

Attending Hyvä Developers Paradise wasn’t just about discovering new tech or hearing the latest product updates. It was about actively participating in a community shaping the future of open-source eCommerce. Magento remains the only valid alternative for those who value customization, flexibility, and robust capabilities. And it’s this community—when united and energized—that can help the platform survive and thrive.

Mage-OS and the Power of Open Collaboration

One of the most exciting aspects of the event was the in-depth, real-time dialogue around Mage-OS—the community-driven fork of Magento. Talking with other developers provided invaluable insights into the platform’s evolution and direction.

Despite coming from different backgrounds, teams, and experiences, everyone shared a common goal: to make Mage-OS a stable, reliable, and forward-thinking alternative.

Some developers have already begun experimenting with Mage-OS in staging environments, while others are even running it in production—evaluating its compatibility with third-party extensions and testing its real-world stability. These trials are critical in identifying strengths, pinpointing gaps, and steering future improvements. The fact that so many professionals are dedicating time and effort to test and contribute to Mage-OS shows how deeply this community believes in its potential.

A Shared Goal That Knows No Borders

One recurring theme in every conversation was the importance of having a shared vision. It doesn’t matter where we come from, what language we speak, or what part of the world we’re coding in. What matters is having a common purpose and moving forward—together.

Meeting other developers face-to-face drove home the point: without unity, we risk fragmentation, which slows progress. It’s the community glue—continuous, open, and constructive dialogue—that holds this ecosystem together. Without it, we risk missing out on the innovations that only collective effort can bring.

Becoming a Voice for the Community

One thing that struck me during the event was how many agencies that have worked with Magento for years still weren’t aware of Mage-OS. That realization pushed me to become more than a user—I became an advocate. I spent time talking to teams, sharing what’s been achieved so far, and encouraging them to use Mage-OS and become part of the journey.

Magento has always had a strong community. However, to grow, the project needs not only developers but also agencies, professionals, and stakeholders to get involved. It’s time to move from passive users to active contributors—whether that means writing code, giving feedback, improving documentation, or simply spreading the word.

As Helen Keller once said:
“Alone, we can do so little; together, we can do so much.”

Beyond Code: Human Connections Matter

Hyvä Developers Paradise wasn’t just about code and tech talks. At its heart, this was an event about people. Yes, there were deep-dive sessions and technical content—but there were also bowling, tennis matches, dance parties, and sunset drinks by the ocean.

These shared moments created bonds that went far beyond the professional. Often, the best ideas come from the most unexpected conversations—over a drink, during a tennis match, or walking along the beach. The real power of the Magento community lies in this, too: the ability to build authentic relationships around a shared passion.

Magento Has a Future—But It’s Up to Us

Hyvä Developers Paradise 2025 was a bold reminder that Magento’s strength isn’t just in the code—it’s in the people who believe in it and commit to improving it daily.

More than an event, this was a statement of purpose: Magento has a bright future—but only if the community stays united, engaged, and committed.

For those working with Magento or curious about the future of open-source eCommerce, events like this aren’t just professional opportunities. They’re a chance to contribute to a mission bigger than any single company or product.

Magento needs its community.
And the community needs Magento.

As Aristotle once said:
“The whole is greater than the sum of its parts.”

Now more than ever, that truth resonates deeply within our community.

The Evolution of Documentation in the Age of AI: A Magento Case Study

anita-miller — Tue, 06 May 2025 00:00:00 GMT

David Lambauer and run_as_root: Innovating Magento Documentation with AI

In the ever-evolving world of e-commerce, documentation remains a critical but often overlooked component. David Lambauer, founder of run_as_root, has been at the forefront of improving Magento documentation through innovative approaches, leveraging AI and open-source collaboration.

Who is David Lambauer?

David Lambauer is a seasoned developer and entrepreneur with a deep passion for open-source software and high-quality development practices. His journey into the tech world began with a traditional German Fachinformatiker apprenticeship (IT Specialist Training), followed by university studies in computer science. However, his real expertise was shaped through hands-on experience in the industry, particularly in Magento development.

How Did He End Up with Magento?

David was introduced to Magento while working at his first workplace, at Netz98, under the mentorship of Christian Münch. His first real test came when he attempted a Magento-related coding challenge. After spending an entire day on it, Münch demonstrated a far more efficient solution in just a few minutes—an eye-opening moment that inspired him to fully commit to learning Magento.

He later expanded his knowledge in infrastructure and scalable systems. These experiences paved the way for him to launch his own agency, run_as_root, with a focus on high-quality Magento solutions.

run_as_root: A New Approach to Magento Development

Founded with the goal of simplifying Magento development, run_as_root emphasizes long-term client relationships and transparency. Unlike traditional agencies that focus on constantly acquiring new clients, run_as_root is dedicated to providing sustainable, well-documented, and high-quality solutions. One of its standout features is its detailed, automated billing system, which ensures that clients know exactly what they’re paying for.

How Did He Develop AI-Generated Magento Documentation?

One of David’s biggest contributions to the Magento community is his work on developer documentation. After Adobe acquired Magento, there was concern over the future of open-source contributions. During this time, David was already contributing to Magento’s DevDocs and saw an opportunity to improve them using automation.

To address this, he created Dev Docs v1.0, a documentation project designed to help new developers get started with Magento.

Using GPT-3.5, he built an AI-powered system that could generate well-structured developer documentation. He based his approach on Laravel’s documentation model, where content is stored as Markdown files in a repository. His process included:

Creating a structured outline of essential Magento topics using AI.
Generating content for each topic with AI assistance.
Formatting everything into Markdown, making it easy to maintain and update.

To make improvements easier, he also added an “Edit on GitHub” button, allowing anyone to contribute fixes or updates. This method leverages a simple reality: people are more likely to correct mistakes than to write new documentation from scratch.

What Were the Challenges?

Despite its success, developing AI-driven documentation wasn’t without obstacles:

Ensuring Accuracy: AI-generated content needed manual review to ensure reliability.
Building a Solid Knowledge Base: The documentation had to cover enough depth to be useful.
Keeping Up with AI Improvements: AI models continue to evolve, meaning the process needs to be updated over time.

David continues to explore new ways to refine AI-generated documentation. One possibility is an AI-assisted query system, where instead of reading static documentation, developers ask an AI assistant questions and receive real-time responses based on well-structured prompts.

How Does He Want to Continue Developing the Documentation?

David sees multiple ways to evolve Magento documentation further:

Enhancing AI-Generated Documentation – Using more advanced AI models like GPT-4 and future iterations to improve content quality, making it more detailed and technically accurate.
AI-Driven Interactive Assistance – Instead of static documentation, an AI-powered chatbot or search tool could provide tailored answers to developer questions in real time.
Crowdsourced Community Contributions – Expanding community involvement by making it easier for developers to suggest edits, provide examples, and validate content.
Integrating Documentation into Development Tools – Embedding documentation directly into developer environments, making it accessible while coding.
Iterative Prompting for Higher Quality – Structuring AI-generated documentation by first defining tone, keywords, reference materials, and output formats before generating final content.

These approaches reflect Lambauer’s commitment to making Magento documentation more dynamic, accessible, and reliable for developers worldwide.

What Does He Like About Magento?

David appreciates Magento for its maturity and strong developer community. Unlike other platforms where basic coding practices are still debated, the Magento ecosystem fully embraces advanced development methodologies like Unit Testing, Integration Testing, and Continuous Integration/Deployment.

He also values Magento’s flexibility and scalability, making it an excellent choice for complex e-commerce solutions. Its open-source nature encourages innovation and long-term community contributions.

What Is His Relation to Mage-OS?

Mage-OS was created in response to the slowdown in Magento’s open-source development after Adobe’s acquisition. David saw Mage-OS as a way to unify the fragmented Magento community, which had been scattered across different Slack groups, regional meetups, and independent developer initiatives.

Seeing the need for better documentation, he took charge of Mage-OS’s documentation project, ensuring that developers have access to up-to-date resources. His work with Mage-OS reinforces his commitment to keeping Magento open-source and community-driven.

Looking Ahead: The Future of Magento Documentation

David Lambauer’s work highlights the power of community-driven innovation in open-source software. His contributions to Magento documentation, combined with modern AI-driven approaches, showcase a new way forward for developer resources.

With run_as_root continuing to push boundaries in Magento development, one key question remains: Is traditional documentation still relevant, or will AI-powered interactive systems take over? No matter the outcome, David and his team are at the forefront of this exciting transformation in developer support.

Mage-OS 1.1: A new admin experience, and so much more!

fabrizio-balliano — Tue, 15 Apr 2025 00:00:00 GMT

We are excited to announce the release of Mage-OS Distribution 1.1.0, a milestone in the development of our community project!

This release packs one huge change, some major ones and many minor security improvements, for the biggest release we’ve ever had!

But first of all, let’s start with…

Our foundation

Mage-OS 1.1 is built on Magento Open Source 2.4.8, and includes all platform updates and community fixes from the upstream release. See the full Magento Open Source 2.4.8 Release Notes for details.

As part of that, Mage-OS 1.1 adds support for PHP 8.4, drops support for PHP 8.1, and requires OpenSearch 2.x going forward.

The latest recommended software versions are:

Composer	2.8
Elasticsearch	— (no longer supported)
OpenSearch	2.19
MariaDB	11.4
MySQL	8.4
PHP	8.4/8.3
RabbitMQ	4
Redis	Valkey 8 (or Redis 7.2+)
Varnish	7.6
Apache	2.4
nginx	1.26

A new backend experience

Thanks to the hard work of Artem Kozynets, one of the members of our community, we’re proud to announce that Mage-OS 1.1 includes a completely redesigned theme for the admin panel!

This is not just a quick style, it’s a complete design system inspired by Material Design 3. The design system is available for you to preview and use on Figma. We would like to extend a huge thank you to Artem for all of his effort and dedication here.

This is such a big change that we’ve dedicated a full blog post to it!

Major performance improvements

In addition to the new admin theme, we’ve chosen to bundle the Creatuity Compiled Interceptors open source module. Thank you to Franciszek Wawrzak for his tireless work creating and maintaining this solution.

This module changes the way Magento 2 generates Interceptor classes (a mechanism that allows plugins to work together), to make plugins faster to execute. This is a drop-in replacement for Magento’s normal interceptor classes. In the process, since Magento uses a lot of plugins, including this lowers the production TTFB (response times) by an average of 10%!

Security improvements and bugfix

Magento 2.4.8 allows for disclosing of all catalog/sales promotion rules, and customer groups, via GraphQL API calls. We believe these details should stay private unless merchants opt in to sharing them. Thanks to Damien Retzinger, Mage-OS 1.1.0 disables these calls.

We also found an error in the calculation of the lowest price of a products when child products are out of stock… and fixed it thanks to Melinda Humphrey.

Thanks to everyone that helped with this release!

Mage-OS wouldn’t exist without a great community. ❤️ Among others, thank you to:

Artem Kozynets
Damien Retzinger
Fabrizio Balliano
Franciszek S Wawrzak
Lucas van Staden
Melinda Humphrey
Ryan Hoerr
Tjitse Efdé
Vinai Kopp

Along with recent Mage-OS Lab contributors:

Antonio Carboni
Christian Münch
Davide Lunardon
Jakub winkler
Luca Fuser
Nils Preuß
Ryan Sun
Samuele Martini
Stefano Tusino

And to everyone that has helped with testing, feedback, and our weekly tech meetings!

Want to participate?

Are you interested in contributing to Mage-OS, or have a bug or improvement you’d like to make? We welcome pull requests at https://github.com/mage-os/mageos-magento2!

If you have a bigger project in mind, please join Discord and chat about your idea. We’d be delighted to hear from you, and help figure out how your idea best fits into Mage-OS!

Installing Mage-OS

You can create a new Mage-OS project with the following SSH command:

composer create-project --repository-url=https://repo.mage-os.org/ mage-os/project-community-edition .

After a successful composer download, you will need to run the installer. Please see DevDocs: Installation Guide for Mage-OS

Moving to Mage-OS

If you are already using Magento 2.4 and PHP 8.2+, you can change to Mage-OS by running the following in SSH:

composer config repositories.0 composer https://repo.mage-os.org/ && 
    composer require mage-os/product-community-edition --no-update && 
    composer remove magento/product-community-edition magento/composer-dependency-version-audit-plugin magento/composer-root-update-plugin --no-update && 
    composer remove sebastian/comparator --dev --no-update && 
    composer update --no-plugins --with-all-dependencies

We strongly recommend updating to the latest Magento version (currently 2.4.8) before changing to Mage-OS, to minimize issues.

Your specific situation may require additional changes to your composer.json file. Generally this will involve changing magento/ package names to mage-os/, or updating dependency versions.

Release: Mage-OS Distribution 1.0.6

fabrizio-balliano — Thu, 13 Feb 2025 00:00:00 GMT

We are excited to announce the release of Mage-OS Distribution 1.0.6!

Release Notes

This release achieves full parity with Magento Open Source 2.4.7-p4, which incorporates critical platform security enhancements.

Please check the release notes for Magento Open Source 2.4.7 and the patch notes for 2.4.7-p4.

You can get Mage-OS from our primary composer repository, repo.mage-os.org.

What’s Changed

Full Changelog: 1.0.5…1.0.6

Thanks to everyone that helped with this release! Including: Fabrizio Balliano, Ryan Hoerr, Vinai Kopp, Lucas van Staden, Francis Gallagher, Tu Van, Peter Jaap Blaakmeer.

Mirror Updates

The latest Magento versions are also available from our public Magento mirror, mirror.mage-os.org:

2.4.4-p12
2.4.5-p11
2.4.6-p9
2.4.7-p4

This mirror composer repository is a drop-in replacement for Magento packages from repo.magento.com. This way you can install Magento without any login, using our public and repeatable build process from the official Magento sources.

Contribute

Are you interested in contributing to Mage-OS, or have a bug or improvement you’d like to make? We welcome pull requests at https://github.com/mage-os/mageos-magento2!

If you have a bigger project in mind, please join Discord and summarize your idea. We’d be delighted to hear from you, and help figure out how your idea best fits into Mage-OS!

Installing Mage-OS

You can create a new Mage-OS project with the following SSH command:

composer create-project --repository-url=https://repo.mage-os.org/ mage-os/project-community-edition .

After a successful composer download, you will need to run the installer. Please see DevDocs: Installation Guide for Mage-OS

Moving to Mage-OS

If you are already using Magento 2.4 and PHP 8.1+, you can change to Mage-OS by running the following in SSH:

composer config repositories.0 composer https://repo.mage-os.org/ && 
    composer require mage-os/product-community-edition --no-update && 
    composer remove magento/product-community-edition magento/composer-dependency-version-audit-plugin magento/composer-root-update-plugin --no-update && 
    composer remove sebastian/comparator --dev --no-update && 
    composer update --no-plugins --with-all-dependencies

We strongly recommend updating to the latest Magento version (currently 2.4.7-p2) before changing to Mage-OS, to minimize issues.

Your specific situation may require additional changes to your composer.json file. Generally this will involve changing magento/ package names to mage-os/, or updating dependency versions.

What’s Next?

Our Vision for Mage-OS

The Mage-OS Distribution is an upstream compatible metapackage based on Magento Open Source. Think of it as an independent version of Magento—based on Magento source code, but including additional changes specific to Mage-OS.

The purpose of the Mage-OS core distribution is to provide

Improved decoupling of packages
Improved developer experience while working with the product
Improved developer experience while contributing to the product
Full compatibility with Magento extensions
Focus on additional security
Reduced infrastructure stack dependencies
Low-level code improvements, for example in the areas of caching and indexing
Removal of most bundled extensions contained in upstream (still independently installable if desired)
A simple documented migration path to Magento Open Source or Adobe Commerce

Mage-OS Distribution releases are made independently of upstream releases. This enables us to move faster when desired, for example when enabling compatibility with new PHP versions.

New functional features will be introduced through independently installable modules. This follows the same decoupling approach that Adobe Commerce is using, allowing for a more stable core and an independent feature module release schedule.

The goal of the reduced infrastructure stack dependencies is to enable new developers to be onboarded more easily. The goal is to be able to use a plain XAMPP stack on any machine, including Windows, to run and develop with Mage-OS. This requires making Elasticsearch optional, as well as ensuring services like Redis, RabbitMQ, Node.js and such remain optional.

Mage-OS will also maintain backwards compatibility and the ability to migrate upstream at multiple levels:

Compatibility with third-party extensions
Database level compatibility (data and schema)
API stability

All of our work on creating custom releases based on Magento is open source, meaning:

Mage-OS builds can be independently built and verified, and are fully reproducible;
If you want to create your own fork and version of Magento or Mage-OS, you can do that too.

That’s all for now!

Transforming Magento: The Power of Community, Contributions, and Innovation

anita-miller — Sat, 08 Feb 2025 00:00:00 GMT

E-commerce is constantly changing, and Magento continues to be a leading platform, providing great tools for developers and businesses. Two exciting additions to this system have recently stood out: the Automatic Translations Module and the PageBuilder Import-Export Module. Created by Davide Lunardon, Luca Fuser and Samuele Martini, these tools aim to make Magento even more useful and easy to use.

The Automatic Translations Module

How It Was Developed

During the Covid period, Samuele Martini began exploring generative AI technologies, particularly OpenAI, with the goal of innovating within e-commerce. An old challenge resurfaced: years ago, a client requested automatic product description generation during ERP imports, which was not feasible at the time.

Fast-forward to a new client of Davide Lunardon, who needed to expand into the French market but lacked translated product data. Given high translation costs and the prospect of further expansions, Samuele and Davide revisited the AI-based module concept, integrating it with DeepL, OpenAI, and Google Gemini to create high-quality translations at a fraction of the cost. The result was an efficient, scalable translation module for Magento.

The module enables the translation of all entities, including products, categories, CMS pages, and static blocks, into almost any language. For the product catalog, it offers two modes: a manual option, accessible via a button in the admin panel, and an automatic mode using cron jobs. The automatic mode includes configurable control systems to prevent the retranslation of manually modified products while allowing forced retranslation if descriptions in the primary language change. Categories, CMS pages, and static blocks, however, can only be translated manually via the admin panel button. Given the module’s effectiveness, we decided to make it available to communities through Mage-OS.

Challenges in Development

Handling HTML in Descriptions – Ensuring AI engines preserved structural elements while translating text was complex.
Prompt Engineering – While DeepL required no prompts, OpenAI and Gemini needed specific instructions to produce quality translations.
Attribute Translation – Unlike textual attributes, select and multiselect attributes store only IDs, requiring a separate translation mechanism.
Alt Text Handling – Since Magento associates alt text with a “gallery” entity, special logic was needed to integrate it seamlessly.

Today, the module allows merchants to translate products, categories, CMS pages, and static blocks either manually or automatically via cron jobs, ensuring efficient multilingual expansion. Recognizing its potential, Samuele and Davide made it available to the Mage-OS community.

PageBuilder Import-Export Module

How It Was Developed

Magento’s PageBuilder is widely used for content management, but one major limitation has always been the inability to export and import CMS pages and blocks between environments. Recognizing this issue, Davide Lunardon proposed an extension to enable seamless content transfers.

The module allows users to export templates as zip files containing:

template.html (HTML content)
preview.jpg (visual representation)
config.xml (metadata configuration)
Children folder (nested CMS blocks)
Asset folder (related images)

Additionally, a Dropbox API integration enables remote template imports. This innovation means merchants can now version and distribute CMS content efficiently across sites.

Challenges in Development

Recursive CMS Dependency Handling – Extracting interdependent assets and templates in a structured manner was a significant challenge.
Choosing the Right Remote Service – A flexible API solution was needed for sustainable integration with Mage-OS.

Supported by fellow developers Luca Fuser and Samuele Martini, Davide’s vision took shape, and the module is now actively being refined for stability and efficiency.

The module was created by Samuele Martini and Davide Lunardon, two experienced developers with a strong background in e-commerce solutions.

About the Developers

Samuele, a developer from Treviso, Italy, has a diverse academic background in statistics, business management, and computer science. After earning his degree from the University of Padua in 2011, he built his career across multiple web agencies, progressing from developer to technical director. In 2025, he decided to start his own business, collaborating with Davide, a longtime friend and former colleague.

Davide is a passionate web developer and an amateur table tennis player. Since becoming a freelancer in late 2020, he has primarily worked with companies and agencies in Italy, bringing his expertise in web development to various projects. Together, Samuele and Davide combined their skills to develop this module, aiming to make translation in e-commerce more efficient and accessible.

How They Discovered Magento

Samuele and Davide’s journey with Magento began at different times, but for similar reasons – its flexibility and power as an e-commerce platform.

Davide first encountered Magento in 2016 while working on projects for one of the companies he was employed at. It was instant love, especially with Magento 1, as Magento 2 was not yet fully stable at the time. The platform’s capabilities and potential drew him in, sparking his deep interest in e-commerce development.

For Samuele, the transition to Magento came as a strategic decision. Initially working on corporate websites with WordPress, he witnessed the agency he worked for pivot toward e-commerce due to the industry’s rapid growth. During their research, they evaluated multiple platforms, including Prestashop, Shopware, and Magento. After a detailed analysis, Samuele recommended Magento because it functioned more like a framework than a traditional CMS, making it ideal for custom, scalable developments. This adaptability made it the perfect choice for handling complex, tailored e-commerce projects.

Their shared passion for Magento eventually led them to specialize in the platform, laying the foundation for their later collaboration and the development of their module.

What They Love About Magento

Both Samuele and Davide appreciate Magento for its robustness, flexibility, and developer-friendly architecture, which makes it a powerful tool for building and maintaining e-commerce platforms.

For Samuele, Magento’s greatest strength is its comprehensiveness. Unlike other platforms that are still catching up on essential features like wishlists and bundled products, Magento has offered these since 2007. From a developer’s perspective, Magento provides an innovative yet intuitive set of patterns that make extending functionality seamless. Features like preferences, plugins, viewModels, virtual types, argument preferences, and dependency injection are unique tools not commonly found in other PHP frameworks, making Magento an extremely versatile and customizable platform.

Davide values Magento’s elasticity and the structured framework that enables scalability and maintainability when managed correctly. The dependency injection system, virtual types, and plugin architecture give developers unparalleled control over customizations. Additionally, its open-source nature allows for deep, ad-hoc integrations tailored to specific business needs. He also highlights the out-of-the-box features that have been present since Magento 1 and continue in Magento 2, making it a large, stable, and complete codebase for e-commerce development. For Davide, working on complex e-commerce projects without Magento would be unimaginable.

Their Relationship with Mage-OS

Mage-OS provides an independent, community-driven environment for Magento development. It ensures that Magento remains open-source and continues evolving with valuable features. Through their contributions, Davide and Samuele have enhanced Magento’s capabilities, making it more accessible and powerful for businesses worldwide. Both Samuele and Davide see Mage-OS as a crucial initiative for preserving and expanding Magento’s open-source ecosystem, allowing them to contribute to the platform in ways that weren’t possible before.

Samuele first learned about Mage-OS through Alessandro Ronchi and was immediately drawn to its clear objectives. He sees its role as twofold: first, ensuring that Magento remains open source, no matter what; and second, enhancing Magento’s core functionality, rather than just integrating Adobe SaaS services. Samuele has actively contributed by working on an AI-powered automatic translation suite alongside Davide, and participating in the OpenAI integration module developed by Ryan Sun.

For Davide, Mage-OS represents freedom – the ability to contribute to Magento without restrictions imposed by corporate ownership. While he acknowledges Adobe’s contributions, he feels that Magento has changed significantly since the acquisition. With Mage-OS, he can now develop and release tools that directly benefit the Magento ecosystem, something he couldn’t do while working within agencies. Seeing how much Magento has shaped his career, he is eager to give back to the community and help restore Magento’s reputation and strength through Mage-OS.

With the Automatic Translations Module and PageBuilder Import-Export Module, Magento developers and merchants can now work more efficiently, scale into new markets, and manage content seamlessly. As Mage-OS grows, these innovations will help shape the future of the Magento ecosystem.

Release: Mage-OS Distribution 1.0.5

fabrizio-balliano — Wed, 06 Nov 2024 00:00:00 GMT

We are excited to announce the release of Mage-OS Distribution 1.0.5!

Release Notes

This release achieves full parity with Magento Open Source 2.4.7-p3, which incorporates critical platform security enhancements.

Please check the release notes for Magento Open Source 2.4.7 and the patch notes for 2.4.7-p3.

You can get Mage-OS from our primary composer repository, repo.mage-os.org.

What’s Changed

Full Changelog: 1.0.4…1.0.5

Mirror Updates

The latest Magento versions are also available from our public Magento mirror, mirror.mage-os.org:

2.4.4-p11
2.4.5-p10
2.4.6-p8
2.4.7-p3

Contribute

Are you interested in contributing to Mage-OS, or have a bug or improvement you’d like to make? We welcome pull requests at https://github.com/mage-os/mageos-magento2!

If you have a bigger project in mind, please join Discord and summarize your idea. We’d be delighted to hear from you, and help figure out how your idea best fits into Mage-OS!

Installing Mage-OS

You can create a new Mage-OS project with the following SSH command:

composer create-project --repository-url=https://repo.mage-os.org/ mage-os/project-community-edition .

After a successful composer download, you will need to run the installer. Please see DevDocs: Installation Guide for Mage-OS

Moving to Mage-OS

If you are already using Magento 2.4 and PHP 8.1+, you can change to Mage-OS by running the following in SSH:

composer config repositories.0 composer https://repo.mage-os.org/ && 
    composer require mage-os/product-community-edition --no-update && 
    composer remove magento/product-community-edition magento/composer-dependency-version-audit-plugin magento/composer-root-update-plugin --no-update && 
    composer remove sebastian/comparator --dev --no-update && 
    composer update --no-plugins --with-all-dependencies

We strongly recommend updating to the latest Magento version (currently 2.4.7-p2) before changing to Mage-OS, to minimize issues.

Your specific situation may require additional changes to your composer.json file. Generally this will involve changing magento/ package names to mage-os/, or updating dependency versions.

What’s Next?

Our Vision for Mage-OS

The purpose of the Mage-OS core distribution is to provide

Improved decoupling of packages
Improved developer experience while working with the product
Improved developer experience while contributing to the product
Full compatibility with Magento extensions
Focus on additional security
Reduced infrastructure stack dependencies
Low-level code improvements, for example in the areas of caching and indexing
Removal of most bundled extensions contained in upstream (still independently installable if desired)
A simple documented migration path to Magento Open Source or Adobe Commerce

Mage-OS Distribution releases are made independently of upstream releases. This enables us to move faster when desired, for example when enabling compatibility with new PHP versions.

Mage-OS will also maintain backwards compatibility and the ability to migrate upstream at multiple levels:

Compatibility with third-party extensions
Database level compatibility (data and schema)
API stability

All of our work on creating custom releases based on Magento is open source, meaning:

Mage-OS builds can be independently built and verified, and are fully reproducible;
If you want to create your own fork and version of Magento or Mage-OS, you can do that too.

That’s all for now!

Release: Mage-OS Distribution 1.0.4

mage-os-team — Thu, 22 Aug 2024 00:00:00 GMT

We are proud to announce Mage-OS Distribution version 1.0.4 is now available!

Release Notes

This Mage-OS update brings parity with Magento Open Source 2.4.7-p2, which was recently released with platform security fixes. When upgrading from an earlier version, please be sure to rotate your encryption key.

Please see the release notes for Magento Open Source 2.4.7 and the patch notes for 2.4.7-p2.

You can get Mage-OS from our primary composer repository, repo.mage-os.org.

What’s Changed

Security changes from upstream 2.4.7-p2 by @rhoerr in #101

Full Changelog: 1.0.3…1.0.4

Mirror Updates

The latest Magento versions are also available from our public Magento mirror, mirror.mage-os.org:

2.4.4-p10
2.4.5-p9
2.4.6-p7
2.4.7-p2

Contributors

Thank you to Ryan Hoerr for managing this release, and to all that contributed to the Magento Open Source security reports and fixes.

Thank you also to all who attend our weekly tech meetings, and to all who have ongoing efforts underway!

Contribute

Are you interested in contributing to Mage-OS, or have a bug or improvement you’d like to make? We welcome pull requests at https://github.com/mage-os/mageos-magento2!

If you have a bigger project in mind, please join Discord and summarize your idea. We’d be delighted to hear from you, and help figure out how your idea best fits into Mage-OS!

Installing Mage-OS

You can create a new Mage-OS project with the following SSH command:

composer create-project --repository-url=https://repo.mage-os.org/ mage-os/project-community-edition .

After a successful composer download, you will need to run the installer. Please see DevDocs: Installation Guide for Mage-OS

Moving to Mage-OS

If you are already using Magento 2.4 and PHP 8.1+, you can change to Mage-OS by running the following in SSH:

composer config repositories.0 composer https://repo.mage-os.org/ && \
    composer require mage-os/product-community-edition --no-update && \
    composer remove magento/product-community-edition magento/composer-dependency-version-audit-plugin magento/composer-root-update-plugin --no-update && \
    composer remove sebastian/comparator --dev --no-update && \
    composer update --no-plugins --with-all-dependencies

We strongly recommend updating to the latest Magento version (currently 2.4.7-p2) before changing to Mage-OS, to minimize issues.

Your specific situation may require additional changes to your composer.json file. Generally this will involve changing magento/ package names to mage-os/, or updating dependency versions.

What’s Next?

Our Vision for Mage-OS

The purpose of the Mage-OS core distribution is to provide

Improved decoupling of packages
Improved developer experience while working with the product
Improved developer experience while contributing to the product
Full compatibility with Magento extensions
Focus on additional security
Reduced infrastructure stack dependencies
Low-level code improvements, for example in the areas of caching and indexing
Removal of most bundled extensions contained in upstream (still independently installable if desired)
A simple documented migration path to Magento Open Source or Adobe Commerce

Mage-OS Distribution releases are made independently of upstream releases. This enables us to move faster when desired, for example when enabling compatibility with new PHP versions.

Mage-OS will also maintain backwards compatibility and the ability to migrate upstream at multiple levels:

Compatibility with third-party extensions
Database level compatibility (data and schema)
API stability

All of our work on creating custom releases based on Magento is open source, meaning:

Mage-OS builds can be independently built and verified, and are fully reproducible;
If you want to create your own fork and version of Magento or Mage-OS, you can do that too.

That’s all for now!

Release: Mage-OS Distribution 1.0.3

ryan-hoerr — Thu, 25 Jul 2024 00:00:00 GMT

We are proud to announce Mage-OS Distribution version 1.0.3 is now available!

Release Notes

This Mage-OS update brings parity with Magento Open Source 2.4.7 and 2.4.7-p1, plus additional contributions particularly to the unit and integration testing suites.

Please see the release notes for Magento Open Source 2.4.7 and the patch notes for 2.4.7-p1.

What’s Changed

Changes and fixes from upstream 2.4.7
Security changes from upstream 2.4.7-p1 by @rhoerr in #98
GitHub Actions
- Add inputs to mage-os/github-actions/coding-standard-baseline by @Tjitse-E in #59
- Add full integration tests workflow by @vpodorozh in #57
- Add Nx integration tests by @adamzero1 in #64
Unit and Integration Test Fixes
- Integration tests/ fix failed tests by @vpodorozh in #61
- Resolve merge conflicts by @Vinai in #87
- Update incorrect dataprovider for Catalog\SortingTest by @vpodorozh in #89
- GraphQl mutation state check | PlaceOrder and Customer actions - skip list adjustments by @vpodorozh in #90
- Skip some of the Bundle tests as the underlying problems are too big … by @vpodorozh in #92
- Fix expireDate formating for integration test by @vpodorozh in #91
- #79 - add shutdown functions wrapper to make sure TestModules will be… by @vpodorozh in #93
- Fix failed tests after the upstream update - db&app isolation were missed by @vpodorozh in #94
- Fix invalid data-sets for unit tests by @vpodorozh in #95
Resolve merge conflict https://github.com/mage-os/mageos-magen… by @vitaliy-golomoziy in #58

Full Changelog: 1.0.1…1.0.3

Contributors

@vitaliy-golomoziy made their first contribution in #58
@vpodorozh made their first contribution in #57

Thank you to all that contributed toward this release, including:

Adam Crossland
Christian Münch
Damien Retzinger
Ihor Sviziev
Jakub Winkler
Max Novik
Ryan Hoerr
Simon Sprankel
Tjitse Efdé
Vinai Kopp
Vladyslav Podorozhnyi

Thank you also to all who attend our weekly tech meetings, and to all who have ongoing efforts underway!

Contribute

Are you interested in contributing to Mage-OS, or have a bug or improvement you’d like to make? We welcome pull requests at https://github.com/mage-os/mageos-magento2!

If you have a bigger project in mind, please join Discord and summarize your idea. We’d be delighted to hear from you, and help figure out how your idea best fits into Mage-OS!

Installing Mage-OS

You can create a new Mage-OS project with the following SSH command:

composer create-project --repository-url=https://repo.mage-os.org/ mage-os/project-community-edition .

After a successful composer download, you will need to run the installer. Please see DevDocs: Installation Guide for Mage-OS

Moving to Mage-OS

If you are already using Magento 2.4 and PHP 8.1+, you can change to Mage-OS by running the following in SSH:

composer config repositories.0 composer https://repo.mage-os.org/ && \
    composer require mage-os/product-community-edition --no-update && \
    composer remove magento/product-community-edition magento/composer-dependency-version-audit-plugin magento/composer-root-update-plugin --no-update && \
    composer remove sebastian/comparator --dev --no-update && \
    composer update --no-plugins --with-all-dependencies

We strongly recommend updating to the latest Magento version (currently 2.4.7-p1) before changing to Mage-OS, to minimize issues.

Your specific situation may require additional changes to your composer.json file. Generally this will involve changing magento/ package names to mage-os/, or updating dependency versions.

What’s Next?

Our Vision for Mage-OS

The purpose of the Mage-OS core distribution is to provide

Improved decoupling of packages
Improved developer experience while working with the product
Improved developer experience while contributing to the product
Full compatibility with Magento extensions
Focus on additional security
Reduced infrastructure stack dependencies
Low-level code improvements, for example in the areas of caching and indexing
Removal of most bundled extensions contained in upstream (still independently installable if desired)
A simple documented migration path to Magento Open Source or Adobe Commerce

Mage-OS Distribution releases are made independently of upstream releases. This enables us to move faster when desired, for example when enabling compatibility with new PHP versions.

Mage-OS will also maintain backwards compatibility and the ability to migrate upstream at multiple levels:

Compatibility with third-party extensions
Database level compatibility (data and schema)
API stability

All of our work on creating custom releases based on Magento is open source, meaning:

Mage-OS builds can be independently built and verified, and are fully reproducible;
If you want to create your own fork and version of Magento or Mage-OS, you can do that too.

That’s all for now!

Introducing the Mage-OS Distribution

mage-os-team — Mon, 09 Oct 2023 00:00:00 GMT

We are proud to announce version 1 of the Mage-OS Distribution!

This release is based on Magento 2.4.6-p3, plus additional contributions including a refreshed admin panel. We will continue making enhancements over time, as they’re contributed by the open source community.

Because they’re based on the same code, all of your existing Magento extensions will work with Mage-OS too!

UPDATE 2023-10-11: With the release of Magento security patch 2.4.6-p3 today, we’ve also published Mage-OS Distribution 1.0.1.

Installing Mage-OS

You can create a new Mage-OS project with the following SSH command:

composer create-project --repository-url=https://repo.mage-os.org/ mage-os/project-community-edition .

After a successful composer download, you will need to run the installer. Please see DevDocs: Installation Guide for Mage-OS

Moving to Mage-OS

If you are already using Magento 2.4 and PHP 8.1+, you can change to Mage-OS by running the following in SSH:

composer config repositories.0 composer https://repo.mage-os.org/ && \
    composer require mage-os/product-community-edition --no-update && \
    composer remove magento/product-community-edition magento/composer-dependency-version-audit-plugin magento/composer-root-update-plugin --no-update && \
    composer remove sebastian/comparator --dev --no-update && \
    composer update --no-plugins --with-all-dependencies

We strongly recommend updating to the latest Magento version (currently 2.4.6-p3) before changing to Mage-OS, to minimize issues.

Your specific situation may require additional changes to your composer.json file. Generally this will involve changing magento/ package names to mage-os/, or updating dependency versions.

Release Notes

This release is based on Magento 2.4.6-p3, plus community contributions merged since. It also includes the following Mage-OS-specific changes:

Removed adobe-commerce/adobe-ims-metapackage, magento/adobe-stock-integration, magento/google-shopping-ads, paypal/module-braintree, temando/module-shipping (thanks to Vinai Kopp)
Admin theme Mage-OS re-brand (thanks to Ryan Hoerr)
Mage-OS brand logo and name changes (thanks to Kiel Pykett)
Fixed Maestro Domestic CC detection pattern to prevent false positives (thanks to Ryan Hoerr)
Increased the default max admin session size to 1 MB (thanks to Ryan Hoerr, and Maciej Tomaszewski and others involved on the upstream discussions)
Faster category product count (thanks to Damien Retzinger, and Vincent Enjalbert who created the original upstream PR)

Huge thank you to everyone that has contributed to the Mage-OS infrastructure, tests, actions, and more to get us here, including:

Vinai Kopp
Damien Retzinger
Daniel Sloof
Adam Crossland
Tjitse Efdé
Gowri Sankar
Vitaliy Golomozy
David Lambauer
Simon Sprankel
Kamlesh Luhana
Kiel Pykett
Christian Münch
Fabian Schmengler
Vladyslav Podorozhnyi
and so many more

What’s Next?

Our Vision for Mage-OS

The purpose of the Mage-OS core distribution is to provide

Improved decoupling of packages
Improved developer experience while working with the product
Improved developer experience while contributing to the product
Full compatibility with Magento extensions
Focus on additional security
Reduced infrastructure stack dependencies
Low-level code improvements, for example in the areas of code generation and caching
Removal of most bundled extensions contained in upstream (they can still be independently installed if desired)
A simple documented migration path to Magento Open Source or Adobe Commerce

Mage-OS Distribution releases are made independently of upstream releases. This enables us to move faster when desired, for example when enabling compatibility with new PHP versions.

Mage-OS will also maintain backwards compatibility and the ability to migrate upstream at multiple levels:

Compatibility with third-party extensions
Database level compatibility (data and schema)
API stability

All of our work on creating custom releases based on Magento is open source, meaning:

Mage-OS builds can be independently built and verified, and are fully reproducible;
If you want to create your own fork and version of Magento or Mage-OS, you can do that too.

Up Next: Mage-OS Flavored Distributions

Soon, we will be working toward producing different ‘flavors’ of Mage-OS. These flavors will be different bundles of Mage-OS packages, for specific purposes. For example:

The Mage-OS headless distribution might contain no storefront theme
The Mage-OS minimal distribution might contain only a minimal set of packages to enable building lightweight applications
The Mage-OS headful distribution might contain no GraphQL packages

Fundamentally these will be the same Mage-OS/Magento you’ve come to know and love, but without features that don’t apply to a given use case — and maybe with additional features that use case uniquely benefits from. In the process, Mage-OS will become more performant, more flexible, and appeal to an even broader market.

Our goal is also to allow others to create their own ‘distributions as ‘flavored’ distributions too.

Contribute

Are you interested in contributing to Mage-OS, or have a bug or improvement you’d like to make? We’re open for pull requests now at https://github.com/mage-os/mageos-magento2!

If you have a bigger project in mind, please join Discord and summarize your idea in #discussions. We’d be delighted to hear from you, and help figure out how your idea best fits into Mage-OS!

That’s all for now!

Magento 2.4.6 Release

ryan-hoerr — Sun, 26 Mar 2023 00:00:00 GMT

The recently-released Magento 2.4.6 (along with 2.4.5-p2, and 2.4.4-p3) is now available on all Mage-OS mirror and distribution repositories. We had to delay the release briefly because of a missing release tag on one of the upstream Magento repositories, which we reported and has since been corrected.

If you’re interested in using a Mage-OS repository, please see the Mage-OS Distribution page!

Currently all packages are exact copies of the official Magento packages for each release. This will change as soon as we release our own Mage-OS Distribution.

Mage-OS Association Progress

We are making progress on establishing the Mage-OS Association. Recently the Polish court fully approved and filed the association in the national registry. We are now working through legal steps for handling of taxes, opening a bank account, and choosing an accountant. We expect to open membership and finances as soon as those steps come together.

Magento 2.4.5-p1 release

mage-os-team — Tue, 11 Oct 2022 00:00:00 GMT

Adobe has released updates to Magento Open Source today, versions 2.4.5-p1 and 2.4.4-p2.

Those same updates are now also available if you’re using our Magento mirror composer repository, mirror.mage-os.org. Our validation has confirmed the mirror releases are installable and match the official releases.

Thanks to Vinai Kopp and Damien Retzinger for managing the release process.

If you’re not yet using the Mage-OS Magento mirror, you can do that today by swapping repo.magento.com to mirror.mage-os.org in your composer.json (unless you require any Magento Marketplace packages). This is a public repository, built by our independent open source build process from the Magento 2 source code. For more info on the Mage-OS nightly and mirror repositories, see: https://mage-os.org/distribution

We have plans to launch the Mage-OS Distribution and start accepting pull requests by the end of this year. Stay tuned for more!

Mirror 2.4.5 release and many contributions

mage-os-team — Mon, 15 Aug 2022 00:00:00 GMT

Work has been progressing nicely, and we celebrate that more people are getting involved! Here is an overview of what has been happening since the last blog post.

Technical topics

Mage-OS Magento® Mirror Distribution

Adobe released Magento Open Source 2.3.7-p4, 2.4.3-p3, 2.4.4-p1 and 2.4.5 on the 9th of August! We are pleased to announce that these versions can now also be installed as independently built packages, using the Mage-OS mirror.

While preparing the releases, we discovered (very few) inconsistencies in upstream composer.json files that broke our build process. We reported these inconsistencies upstream to Adobe (for example in the security package and adobe-stock-integration repositories), and they are being addressed. At the same time, we have improved the build tool to account for these issues allowing Mage-OS to become more independent.

Finally, Damien Retzinger from Graycore contributed GitHub actions to automate testing builds in parallel. This allowed us to move much, much faster, and we are very grateful for his participation!

Daniel Sloof created GitHub actions to check the integrity of the Mage-OS packages against the upstream releases. This QA tooling is invaluable.

Many thanks to Damien and Daniel, and to all others like Anton, Daniel Fahlke and many others who participated in discussions and helped with good ideas in the #tech channel or joined a stream on Discord.

Mage-OS Magento® Mirror Nightly Builds

The new versioning scheme for the nightly build packages, as discussed in the previous post, has been implemented, and is currently being evaluated, if it indeed serves the desired purpose.
We expect the nightly builds to be available soon.

Contributing

People have been asking how to contribute. It is very encouraging to see that many people want to help, and so far we still don’t have a good answer.

Since we are currently “meta-building”, instead of building Magento features and improvements, we are in a bit of a special situation. We expect this to change once the infrastructure for the mirror, nightly builds, and the Mage-OS distribution is closer to complete.

The usual approach to encouraging contributions to open source projects is to do “Issue grooming” and then to choose tickets that are good first issues. This approach is not applicable (yet) to the Mage-OS project.

At the moment, most people have started by joining Discord, following the #tech channel, and joining streams in the #Watercooler channels, where problems are being discussed and solved together.

It has been very valuable to interact in this way.

Currently, this is the best way to get started, as it helps develop an understanding of what is required at a given moment in time, be it debugging, writing code, pairing or coming up with ideas.

So if you are interested in helping, join a stream in Discord and get an idea what is happening. It is fun, too, if you like problem-solving and coding :)

For those who simply wish to keep up, start by following the discord #tech channel.

We are welcoming and inclusive at chat.mage-os.org!

Organizational topics

Mage-OS Association

Vacation season is keeping us busy, but we are moving to complete the founding of the association.

We will form a committee to set the price for members and supporting members (companies).
If you would like to be involved, please join the Mage-OS Discord #membership channel and let us know!

For now that’s all, more updates are coming soon.

The Mage-OS folks