NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist · #3034 most downloaded on Packagist
Magento 2 merchandising and search engine built on ElasticSearch
Last release 6 days ago
02 Oct 2026
Ships fairly regularly
a new release about every 5 weeks
Rarely documented
notes for 14 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
11 years old
234 releases · first in 2016
[CatalogRule] Fix #3920 , prevent StyleSmuggler-like vulnerability (backport of AC-2571) in Conditions controller by @vahonc in #3921
This release introduces the Recommender Explain module to help you preview from the Magento Admin interface the behavior of the Elasticsuite Premium Recommender module.
It provides feedback about whether a recommendation is coming from manual selection (from the product edit page) or through the behavioral data based rules and also allows you to test a different configuration for a given recommendation type (Related Products, Upsell, Cross-sell).
We will build up upon this module in the coming releases to add more contextual information (which behavioral rule(s) a product matched, how the score is computed, etc).
You can install that Smile_ElasticsuiteRecommenderExplain module single-handedly by requiring the package smile/module-elasticsuite-recommender-explain through composer with the correct "Elasticsuite Branch-version" syntax, that is
| Magento version | Elasticsuite | Installation |
|---|---|---|
| <2.4.6 | 2.10.x | composer require [--ignore-platform-reqs] smile/module-elasticsuite-recommender-explain ~2.10.0 |
| >=2.4.6 && <2.4.9 | 2.11.x | composer require [--ignore-platform-reqs] smile/module-elasticsuite-recommender-explain ~2.11.0 |
| >=2.4.9 | 2.12.x | composer require [--ignore-platform-reqs] smile/module-elasticsuite-recommender-explain ~2.12.0 |
You will also automatically benefit from the module if you upgrade our Elasticsuite Premium metapackage
| Magento flavour | Metapackage upgrade |
|---|---|
| Community Edition / Magento | composer update --with-all-dependencies smile/elasticsuite-premium-magento |
| Enterprise Edition / Adobe Commerce | composer update --with-all-dependencies smile/elasticsuite-premium-commerce |
As a reminder, to install our metapackage for the first time
| Magento version | Metapackage first-time install in Community Edition / Magento |
|---|---|
| <2.4.6 | composer require [--ignore-platform-reqs] --with-all-dependencies smile/elasticsuite-premium-magento ~2.10.0 |
| >=2.4.6 && <2.4.9 | composer require [--ignore-platform-reqs] --with-all-dependencies smile/elasticsuite-premium-magento ~2.11.0 |
| >=2.4.9 | composer require [--ignore-platform-reqs] --with-all-dependencies smile/elasticsuite-premium-magento ~2.12.0 |
| Magento version | Metapackage first-time install in Enterprise Edition / Adobe Commerce |
|---|---|
| <2.4.6 | composer require [--ignore-platform-reqs] --with-all-dependencies smile/elasticsuite-premium-commerce ~2.10.0 |
| >=2.4.6 && <2.4.9 | composer require [--ignore-platform-reqs] --with-all-dependencies smile/elasticsuite-premium-commerce ~2.11.0 |
| >=2.4.9 | composer require [--ignore-platform-reqs] --with-all-dependencies smile/elasticsuite-premium-commerce ~2.12.0 |
The context information blocks (list of synonyms, optimizers, popular searches, ...) of the Explain screen are now located in a resizeable side panel to limit the amount elements to scroll over to reach the preview results from the Explain parameters form.
Above the preview results, there is also now an "Ignore optimizers" checkbox that allows you to re-run the same preview but without applying any of the applicable optimizers.
This can be useful when you want to have an idea of the pure, unaltered fulltext scores of products for a given search term(s).
Up until now, changing properties such as searchability, search weight, or search analyzer for category attributes required database changes or an elasticsuite_indices.xml override.
This release introduces a CSV import/export mechanism for category attributes Elasticsuite properties, similar to the one already existing for product attributes.
It is available through
The simple HTML select provided as Company filter on the Search Usage analytics for Magento B2B users since releases 2.10.24 and 2.11.10 has been upgraded to a search-as-you-type UI component to benefit user with hundreds and hundreds of registered companies.
When there are some failed Elasticsuite Health Checks (Elasticsuite > System > Healthcheck), the Elasticsuite admin menu entry is decorated with a red bubble and the total number of failed checks :
Up until now, that happened whatever the severity level (Notice < Warning < Error < Critical) of the failed checks.
A new setting has been introduced in Store > Configuration > Elasticsuite > Base Settings > Healthchecks > Minimum Severity for Menu Decoration to allow you to only display that red bubble on the Elasticsuite menu entry if there are failed checks at and beyond a certain severity level.
For instance, by selecting Warning (meaning "Warning and above"), the red bubble will not show up on the Elasticsuite menu entry if failed health checks are all at the Notice severity level (it will still be present on the Elasticsuite > Healthcheck menu entry, though).
Full Changelog: 2.12.1.1...2.12.2
One column per quarter.
⛔ ⛔ This is an invalid release superseded by 2.12.1.1 correctly built on top of 2.12.x for Magento 2.4.9+ ⛔ ⛔
[Core] Fix #3884 , Search Relevance null array offset deprecation warning by @vahonc in #3886
Full Changelog: 2.12.0...2.12.1-rc1
Magento 2.4.9 was officially released two weeks ago with, sadly, some breaking changes that were not present in the its latest beta because we all nee…
Magento 2.4.9 was officially released two weeks ago with, sadly, some breaking changes that were not present in the its latest beta because we all need a bit of fun and adventure in our lives /s.
Since some fixes were not possible to integrate in the 2.11.x branch (which was already stretched on a wide range of PHP, MySQL/MariaDB and Elasticsearch/OpenSearch versions, let's be honest), the location of 2.4.9+ Elasticsuite compatibility will be the 2.12.x branch and this is its first official 2.12.0 release.
To enable the highlighting of matched text in the popular term and product autocomplete search results, new settings are available in Elasticsuite Premium at
The feature is available both in the legacy React-based and Vanilla JS InstantSearch autocomplete.
For popular terms, the text matching the initial user query is highlighted.
For products, the text matching the actual search term(s) used to search for products is highlighted, so the behavior will vary according to the situation and the search terms expansion rules dictated by the settings below Stores > Configuration > Elasticsuite > Autocomplete > Advanced Settings.
The example shown below reflects the default settings where the products found are those matching the popular search term "yoga bag", thus both term "yoga" and "bag" highlighted in the visible products.
Future releases might provide
We've introduced a few releases ago the CLI bin/magento interactive command elasticsuite:category-position:migrate to allow you to migrate your legacy product positioning in categories to the Elasticsuite specific positioning.
This release adds an interactive step where you can restrict the number of original positions to retain per category.
/var/www/html $ php bin/magento elasticsuite:category-position:migrate
Transfer negative positions to positive and contiguous ones? (y/n) [default: n] y
Transfer zero positions? (y/n) [default: n] n
Transfer positive positions? (y/n) [default: y] y
It can be useful to set a limit on the number of positions to migrate per category, since you probably want to only make sure that:
- the first page of products is migrated as is ;
- or even better, the first two rows of the first page
to let your optimizers merchandise the rest automatically.
Setting a low limit also avoids slowing down category pages in the BO
Maximum number of positions (negative then positive) per category to migrate (leave blank for all matching positions): 5
This is particularly useful if you have a catalog with a significant size and some categories with a lot of products positioned, to avoid the performance issues associated with the Elasticsuite category preview having to deal with more than 200 or even 500 products positioned.
This is also a way for you, on a per-category basis for instance, to try relying more and more on the Optimizers feature to merchandise your categories.
To improve your site FCP (First Contentful Paint) score, the InstantSearch Vanilla JS components are now loaded with defer by default.
The React version of the InstantSearch will follow in an upcoming release.
Please be advised that regarding the Elasticsuite tracker, for the time being, it is not possible to relocate and use delayed (defer) or asynchronous (async) execution for the two render-blocking scripts located in the <head>.
Full Changelog: 2.11.18.1...2.12.0
[CatalogRule] Fix #3920 , prevent StyleSmuggler-like vulnerability (backport of AC-2571) in Conditions controller by @vahonc in #3921
This release introduces the Recommender Explain module to help you preview from the Magento Admin interface the behavior of the Elasticsuite Premium Recommender module.
It provides feedback about whether a recommendation is coming from manual selection (from the product edit page) or through the behavioral data based rules and also allows you to test a different configuration for a given recommendation type (Related Products, Upsell, Cross-sell).
We will build up upon this module in the coming releases to add more contextual information (which behavioral rule(s) a product matched, how the score is computed, etc).
You can install that Smile_ElasticsuiteRecommenderExplain module single-handedly by requiring the package smile/module-elasticsuite-recommender-explain through composer with the correct "Elasticsuite Branch-version" syntax, that is
| Magento version | Elasticsuite | Installation |
|---|---|---|
| <2.4.6 | 2.10.x | composer require [--ignore-platform-reqs] smile/module-elasticsuite-recommender-explain ~2.10.0 |
| >=2.4.6 && <2.4.9 | 2.11.x | composer require [--ignore-platform-reqs] smile/module-elasticsuite-recommender-explain ~2.11.0 |
| >=2.4.9 | 2.12.x | composer require [--ignore-platform-reqs] smile/module-elasticsuite-recommender-explain ~2.12.0 |
You will also automatically benefit from the module if you upgrade our Elasticsuite Premium metapackage
| Magento flavour | Metapackage upgrade |
|---|---|
| Community Edition / Magento | composer update --with-all-dependencies smile/elasticsuite-premium-magento |
| Enterprise Edition / Adobe Commerce | composer update --with-all-dependencies smile/elasticsuite-premium-commerce |
As a reminder, to install our metapackage for the first time
| Magento version | Metapackage first-time install in Community Edition / Magento |
|---|---|
| <2.4.6 | composer require [--ignore-platform-reqs] --with-all-dependencies smile/elasticsuite-premium-magento ~2.10.0 |
| >=2.4.6 && <2.4.9 | composer require [--ignore-platform-reqs] --with-all-dependencies smile/elasticsuite-premium-magento ~2.11.0 |
| >=2.4.9 | composer require [--ignore-platform-reqs] --with-all-dependencies smile/elasticsuite-premium-magento ~2.12.0 |
| Magento version | Metapackage first-time install in Enterprise Edition / Adobe Commerce |
|---|---|
| <2.4.6 | composer require [--ignore-platform-reqs] --with-all-dependencies smile/elasticsuite-premium-commerce ~2.10.0 |
| >=2.4.6 && <2.4.9 | composer require [--ignore-platform-reqs] --with-all-dependencies smile/elasticsuite-premium-commerce ~2.11.0 |
| >=2.4.9 | composer require [--ignore-platform-reqs] --with-all-dependencies smile/elasticsuite-premium-commerce ~2.12.0 |
The context information blocks (list of synonyms, optimizers, popular searches, ...) of the Explain screen are now located in a resizeable side panel to limit the amount elements to scroll over to reach the preview results from the Explain parameters form.
Above the preview results, there is also now an "Ignore optimizers" checkbox that allows you to re-run the same preview but without applying any of the applicable optimizers.
This can be useful when you want to have an idea of the pure, unaltered fulltext scores of products for a given search term(s).
Up until now, changing properties such as searchability, search weight, or search analyzer for category attributes required database changes or an elasticsuite_indices.xml override.
This release introduces a CSV import/export mechanism for category attributes Elasticsuite properties, similar to the one already existing for product attributes.
It is available through
The simple HTML select provided as Company filter on the Search Usage analytics for Magento B2B users since releases 2.10.24 and 2.11.10 has been upgraded to a search-as-you-type UI component to benefit user with hundreds and hundreds of registered companies.
When there are some failed Elasticsuite Health Checks (Elasticsuite > System > Healthcheck), the Elasticsuite admin menu entry is decorated with a red bubble and the total number of failed checks :
Up until now, that happened whatever the severity level (Notice < Warning < Error < Critical) of the failed checks.
A new setting has been introduced in Store > Configuration > Elasticsuite > Base Settings > Healthchecks > Minimum Severity for Menu Decoration to allow you to only display that red bubble on the Elasticsuite menu entry if there are failed checks at and beyond a certain severity level.
For instance, by selecting Warning (meaning "Warning and above"), the red bubble will not show up on the Elasticsuite menu entry if failed health checks are all at the Notice severity level (it will still be present on the Elasticsuite > Healthcheck menu entry, though).
Full Changelog: 2.11.20...2.11.21
[Core] Fix #3884 , Search Relevance null array offset deprecation warning by @vahonc in #3886
Full Changelog: 2.11.19...2.11.20
[Core] Fix #3884 , Search Relevance null array offset deprecation warning by @vahonc in #3886
Full Changelog: 2.11.19...2.11.20-rc1
💎 Highlighting of autocomplete search results
To enable the highlighting of matched text in the popular term and product autocomplete search results, new settings are available in Elasticsuite Premium at
The feature is available both in the legacy React-based and Vanilla JS InstantSearch autocomplete.
For popular terms, the text matching the initial user query is highlighted.
For products, the text matching the actual search term(s) used to search for products is highlighted, so the behavior will vary according to the situation and the search terms expansion rules dictated by the settings below Stores > Configuration > Elasticsuite > Autocomplete > Advanced Settings.
The example shown below reflects the default settings where the products found are those matching the popular search term "yoga bag", thus both term "yoga" and "bag" highlighted in the visible products.
Future releases might provide
We've introduced a few releases ago the CLI bin/magento interactive command elasticsuite:category-position:migrate to allow you to migrate your legacy product positioning in categories to the Elasticsuite specific positioning.
This release adds an interactive step where you can restrict the number of original positions to retain per category.
/var/www/html $ php bin/magento elasticsuite:category-position:migrate
Transfer negative positions to positive and contiguous ones? (y/n) [default: n] y
Transfer zero positions? (y/n) [default: n] n
Transfer positive positions? (y/n) [default: y] y
It can be useful to set a limit on the number of positions to migrate per category, since you probably want to only make sure that:
- the first page of products is migrated as is ;
- or even better, the first two rows of the first page
to let your optimizers merchandise the rest automatically.
Setting a low limit also avoids slowing down category pages in the BO
Maximum number of positions (negative then positive) per category to migrate (leave blank for all matching positions): 5
This is particularly useful if you have a catalog with a significant size and some categories with a lot of products positioned, to avoid the performance issues associated with the Elasticsuite category preview having to deal with more than 200 or even 500 products positioned.
This is also a way for you, on a per-category basis for instance, to try relying more and more on the Optimizers feature to merchandise your categories.
To improve your site FCP (First Contentful Paint) score, the InstantSearch Vanilla JS components are now loaded with defer by default.
The React version of the InstantSearch will follow in an upcoming release.
Please be advised that regarding the Elasticsuite tracker, for the time being, it is not possible to relocate and use delayed (defer) or asynchronous (async) execution for the two render-blocking scripts located in the <head>.
Full Changelog: 2.11.18.1...2.11.19
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
[CatalogRule] Fix #3920 , prevent StyleSmuggler-like vulnerability (backport of AC-2571) in Conditions controller by @vahonc in #3921
This release introduces the Recommender Explain module to help you preview from the Magento Admin interface the behavior of the Elasticsuite Premium Recommender module.
It provides feedback about whether a recommendation is coming from manual selection (from the product edit page) or through the behavioral data based rules and also allows you to test a different configuration for a given recommendation type (Related Products, Upsell, Cross-sell).
We will build up upon this module in the coming releases to add more contextual information (which behavioral rule(s) a product matched, how the score is computed, etc).
You can install that Smile_ElasticsuiteRecommenderExplain module single-handedly by requiring the package smile/module-elasticsuite-recommender-explain through composer with the correct "Elasticsuite Branch-version" syntax, that is
| Magento version | Elasticsuite | Installation |
|---|---|---|
| <2.4.6 | 2.10.x | composer require [--ignore-platform-reqs] smile/module-elasticsuite-recommender-explain ~2.10.0 |
| >=2.4.6 && <2.4.9 | 2.11.x | composer require [--ignore-platform-reqs] smile/module-elasticsuite-recommender-explain ~2.11.0 |
| >=2.4.9 | 2.12.x | composer require [--ignore-platform-reqs] smile/module-elasticsuite-recommender-explain ~2.12.0 |
You will also automatically benefit from the module if you upgrade our Elasticsuite Premium metapackage
| Magento flavour | Metapackage upgrade |
|---|---|
| Community Edition / Magento | composer update --with-all-dependencies smile/elasticsuite-premium-magento |
| Enterprise Edition / Adobe Commerce | composer update --with-all-dependencies smile/elasticsuite-premium-commerce |
As a reminder, to install our metapackage for the first time
| Magento version | Metapackage first-time install in Community Edition / Magento |
|---|---|
| <2.4.6 | composer require [--ignore-platform-reqs] --with-all-dependencies smile/elasticsuite-premium-magento ~2.10.0 |
| >=2.4.6 && <2.4.9 | composer require [--ignore-platform-reqs] --with-all-dependencies smile/elasticsuite-premium-magento ~2.11.0 |
| >=2.4.9 | composer require [--ignore-platform-reqs] --with-all-dependencies smile/elasticsuite-premium-magento ~2.12.0 |
| Magento version | Metapackage first-time install in Enterprise Edition / Adobe Commerce |
|---|---|
| <2.4.6 | composer require [--ignore-platform-reqs] --with-all-dependencies smile/elasticsuite-premium-commerce ~2.10.0 |
| >=2.4.6 && <2.4.9 | composer require [--ignore-platform-reqs] --with-all-dependencies smile/elasticsuite-premium-commerce ~2.11.0 |
| >=2.4.9 | composer require [--ignore-platform-reqs] --with-all-dependencies smile/elasticsuite-premium-commerce ~2.12.0 |
The context information blocks (list of synonyms, optimizers, popular searches, ...) of the Explain screen are now located in a resizeable side panel to limit the amount elements to scroll over to reach the preview results from the Explain parameters form.
Above the preview results, there is also now an "Ignore optimizers" checkbox that allows you to re-run the same preview but without applying any of the applicable optimizers.
This can be useful when you want to have an idea of the pure, unaltered fulltext scores of products for a given search term(s).
Up until now, changing properties such as searchability, search weight, or search analyzer for category attributes required database changes or an elasticsuite_indices.xml override.
This release introduces a CSV import/export mechanism for category attributes Elasticsuite properties, similar to the one already existing for product attributes.
It is available through
The simple HTML select provided as Company filter on the Search Usage analytics for Magento B2B users since releases 2.10.24 and 2.11.10 has been upgraded to a search-as-you-type UI component to benefit user with hundreds and hundreds of registered companies.
When there are some failed Elasticsuite Health Checks (Elasticsuite > System > Healthcheck), the Elasticsuite admin menu entry is decorated with a red bubble and the total number of failed checks :
Up until now, that happened whatever the severity level (Notice < Warning < Error < Critical) of the failed checks.
A new setting has been introduced in Store > Configuration > Elasticsuite > Base Settings > Healthchecks > Minimum Severity for Menu Decoration to allow you to only display that red bubble on the Elasticsuite menu entry if there are failed checks at and beyond a certain severity level.
For instance, by selecting Warning (meaning "Warning and above"), the red bubble will not show up on the Elasticsuite menu entry if failed health checks are all at the Notice severity level (it will still be present on the Elasticsuite > Healthcheck menu entry, though).
Full Changelog: 2.10.35...2.10.36
[Core] Fix #3884 , Search Relevance null array offset deprecation warning by @vahonc in #3886
Full Changelog: 2.10.34...2.10.35
[Core] Fix #3884 , Search Relevance null array offset deprecation warning by @vahonc in #3886
Full Changelog: 2.10.34...2.10.35-rc1
💎 Highlighting of autocomplete search results
To enable the highlighting of matched text in the popular term and product autocomplete search results, new settings are available in Elasticsuite Premium at
The feature is available both in the legacy React-based and Vanilla JS InstantSearch autocomplete.
For popular terms, the text matching the initial user query is highlighted.
For products, the text matching the actual search term(s) used to search for products is highlighted, so the behavior will vary according to the situation and the search terms expansion rules dictated by the settings below Stores > Configuration > Elasticsuite > Autocomplete > Advanced Settings.
The example shown below reflects the default settings where the products found are those matching the popular search term "yoga bag", thus both term "yoga" and "bag" highlighted in the visible products.
Future releases might provide
We've introduced a few releases ago the CLI bin/magento interactive command elasticsuite:category-position:migrate to allow you to migrate your legacy product positioning in categories to the Elasticsuite specific positioning.
This release adds an interactive step where you can restrict the number of original positions to retain per category.
/var/www/html $ php bin/magento elasticsuite:category-position:migrate
Transfer negative positions to positive and contiguous ones? (y/n) [default: n] y
Transfer zero positions? (y/n) [default: n] n
Transfer positive positions? (y/n) [default: y] y
It can be useful to set a limit on the number of positions to migrate per category, since you probably want to only make sure that:
- the first page of products is migrated as is ;
- or even better, the first two rows of the first page
to let your optimizers merchandise the rest automatically.
Setting a low limit also avoids slowing down category pages in the BO
Maximum number of positions (negative then positive) per category to migrate (leave blank for all matching positions): 5
This is particularly useful if you have a catalog with a significant size and some categories with a lot of products positioned, to avoid the performance issues associated with the Elasticsuite category preview having to deal with more than 200 or even 500 products positioned.
This is also a way for you, on a per-category basis for instance, to try relying more and more on the Optimizers feature to merchandise your categories.
To improve your site FCP (First Contentful Paint) score, the InstantSearch Vanilla JS components are now loaded with defer by default.
The React version of the InstantSearch will follow in an upcoming release.
Please be advised that regarding the Elasticsuite tracker, for the time being, it is not possible to relocate and use delayed (defer) or asynchronous (async) execution for the two render-blocking scripts located in the <head>.
Full Changelog: 2.10.33.1...2.10.34
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →