Skip to main content
Version: 3.x

Release notes

This page lists the changes between each Front-Commerce minor release.

Latest version​

Front-Commerce 3.9.0

Compatible with:

  • Node.js:: ^20.12.0
  • Gezy: v11
  • Magento2: 2.4.4 -> 2.4.6-p3 (Open Source & Commerce & B2B)
  • Magento1: CE 1.7+, EE 1.12+, OpenMage LTS 19.4+

Semantic Versioning​

We aim at releasing often and follow Semantic Versioning to clearly communicate our advancements to developers. We document each migration process (changelog, release notes and documentation updates) and add deprecation warnings while keeping backwards compatibility to keep upgrades as seamless as possible.

TL;DR: (from the Semantic Versioning documentation)

Given a version number MAJOR.MINOR.PATCH, increment the:

  1. MAJOR version when you make incompatible API changes,
  2. MINOR version when you add functionality in a backwards compatible manner, and
  3. PATCH version when you make backwards compatible bug fixes.

Additional labels for pre-release can (and in our case will) be added to the MAJOR.MINOR.PATCH format.

Each supported version will receive bug fixes and security updates, leading to regular patch releases.

Release Schedule​

We release a minor version of Front-Commerce every 6 weeks with new features, tech improvements, bug fixes…

In order to follow the pace of our users, we may release intermediate pre-releases (-beta.x) between 2 minor releases, to allow early-adopters to integrate the features as soon as possible and to give us feedback.

The table below shows the exact dates of the upcoming releases and our Long Term Support (LTS) policy.

There are three phases that a Front-Commerce release can be in: Current, End of Support (EOS), and End of Life (EOL)
  • Current - Should incorporate most of the non-major (non-breaking) changes that land on Front-Commerce main branch.
  • End of Support - While still in the EOS phase, the release will receive critical bug fixes and security updates. New features will not be added to EOS releases. The EOS phase will last for 1 year after the release date.
  • End of Life - While still in the EOL phase, the release will receive critical security updates. No new features or bug fixes will be added to EOL releases. The EOL phase will last for 2 year after the release date.
VersionRelease dateEnd of Support (EOS)End of Life (EOL)
3.10.02025-01-022026-01-022027-01-02
3.9.02024-11-212025-11-212026-11-21
3.8.02024-10-102025-10-102026-10-10
3.7.02024-08-292025-08-292026-08-29
3.6.02024-07-182025-07-182026-07-18
3.5.02024-06-062025-06-062026-06-06
3.4.02024-04-252025-04-252026-04-25
3.3.02024-02-012025-02-012026-02-01
3.2.02024-01-082025-01-082026-01-08
3.1.02023-11-20⚠️ 2024-11-202025-11-20
3.0.02023-09-28⚠️ 2024-09-282025-09-28

3.9.0 (2024-11-21)​

This release introduces Google Consent Mode V2, Consistent Price Display, Gezy advanced capabilities and Extension Features AP

3.8.0 (2024-10-10)​

This release marks a major milestone for our Gezy integration, introducing core e-commerce functionalities.

3.7.0 (2024-08-29)​

This release introduces te foundations for the Gezy integration and several bug fixes to improve the overall stability of the platform.

3.6.0 (2024-07-18)​

This release introduces a revamped Maintenance Mode, convenients API to define Cache-Control and Server-Timing headers to improve performance and monitoring. It also includes several bug fixes to improve developer experience and the overall stability of the platform.

3.5.0 (2024-06-06)​

This release add the quick order page which and different ways to switch to server-side tracking to cope with the decline of 3rd-party cookies.
It also contains dynamic routing, built on top of the Remix/React-Router routes API.

3.4.0 (2024-04-25)​

We migrated to Vite, a faster development tool providing a significantly improved development experience with instant feedback. We introduced new features like stabilized public core APIs, new payment modules, and enhanced testing.

3.3.0 (2024-02-01)​

The release introduces event-driven architectural components, extension features, public configurations, and automatic session commit. It also includes core enhancements and smaller convenient features. It sets the technical foundations for future developments and enables the development of event-based features in applications.

3.2.0 (2024-01-08)​

This updates includes some bug fixes and improvements to the core. Notably, new packages such as @front-commerce/magento1, @front-commerce/adyen and @front-commerce/akamai-image-manager are now available. The Magic Button and Contribution technical foundations have been revamped to embrace Web standards.

3.1.0 (2023-11-20)​

This update includes several core stabilization fixes, a new PWA assets generation API, useCart and useCustomer hooks and Magento2 order filtering. It also features Attraqt Datasource Compatibility for Magento1, extended support for product reviews to Magento1, and facets order customization for Magento1. Additionally, the update improves the performance of adding multiple items to the cart in Magento2, particularly beneficial for Adobe Commerce B2B projects

3.0.0 (2023-09-28)​

We are excited to introduce Front-Commerce 3.0, a big leap forward in e-commerce development. With a focus on web performance, developer experience, and adherence to web standards, this release is set to redefine how you approach building your online storefronts.

Front-Commerce is a storefront for headless commerce based on the newly released Remix v2 framework. We're bringing all the goodness we developed over the past 7 years, to the Remix ecosystem.

In this release, we've merged both technologies to enhance the experience for end users and developers alike.