Medusa v2.22.2 introduces an official beta Adyen payment provider, major search improvements, and a comprehensive round of dependency updates. Developers should note behavior changes in BigNumber and body-parser validation that may cause custom code to throw errors instead of returning fallback values.
v2.22.1 adds the ability to update payment session client data after creation and seeds the fa-IR locale as the default translation, while delivering numerous bug fixes and UI improvements across the dashboard and core flows. The update is a routine patch with no breaking changes, allowing developers to adopt it safely without migration effort.
Medusa v2.22.0 introduces support for Node.js v22.22.0 or later, dropping support for the end-of-life Node.js 20 runtime. It also adds new capabilities like admin customer CSV exports and multiple payment provider accounts.
Medusa v2.21.1. Source highlight: The Search Module allows you to manage and search through indexes defined in your Medusa application. You can search products or any data model defined just by defining an index for it.
Medusa v2.21.0. Source highlight: This release brings security improvements to the Store API, specifically related to what relations and fields can be retrieved through the routes. We recommend all Medusa stores update to this version.
Medusa v2.17.0. Source highlight: **IMPORTANT:** This release contains a regression around worker instances. You should not upgrade to this but instead 2.17.1.
Medusa v2.16.0. Source highlight: This release comes with many improvements and bug fixes. We highly recommend updating to leverage these changes in your application.
Medusa v2.14.0. Source highlight: This release open sources the Loyalty plugin and includes breaking changes related to Zod, account creation, and more. Please read carefully before updating.
Medusa v2.13.6. Source highlight: This release includes an update for MikroORM dependencies to v6.6.12 due to recent security vulnerabilities. While Medusa's core API routes were not impacted by the security vulnerability as they're guarded with Zod validation, it may impact custom API routes if they're not properly guarded. So, we
Medusa v2.13.2. Source highlight: ⚠️ Warning: v2.13.2 introduces a regression that causes req.queryConfig to include entity: undefined, which can break routes that spread req.queryConfig into query.graph() (e.g., query.graph({entity: "some_entity", ...req.queryConfig })), resulting in a Service with alias "undefined" was not found e
Medusa v2.12.1. Source highlight: This release fixes a regression in the events system introduced in https://github.com/medusajs/medusa/pull/14084. That PR added an optimization to emit events only when at least one subscriber is registered for the event.
Medusa v2.10.1. Source highlight: We identified a performance regression affecting cart operations in the latest release. This issue resulted in slower response times for cart-related HTTP requests. The regression was caused by a change introduced to control concurrency in cart operations, which inadvertently impacted performance.
Medusa v2.10.0. Source highlight: This release contains breaking changes, so please read the release notes carefully. The breaking changes are all the result of fixing behavior that has not worked as intended until now.