Medusa 2.22.7: stable translations, cross-module joins and what to test
Medusa 2.22.7 ships the Translation Module by default, replaces the Index Module with cross-module joins and adds promotion events. Here is what to test.
- Medusa.js
- Migrations
- Magento 2
- Operations

A store with three languages and a busy promotions calendar runs into the same two problems on almost any platform. Translated content goes stale, and discounts stack in ways nobody intended. On Magento 2 you handle the first with store views and the second with catalog and cart price rules, and you've learned where both of them break. On Medusa, until recently, translations meant either a beta module or a CMS bolted on beside the catalog. Promotions changed without telling the rest of your system.
Medusa v2.22.7 addresses both. The Translation Module is out of beta and installed by default. Cross-module joins replace the Index Module for filtering across module boundaries. Promotions, promotion rules and campaigns now emit events. The release also carries a security fix and a long list of promotion and pricing bug fixes, which matter more to a running store than the headline features do.
The Translation Module is now part of every install
According to the release notes, the Translation Module "is out of beta [and] is now installed in all Medusa projects by default." It covers products, categories, custom data models and more.
For a team moving off Magento 2, this changes the plan. Store views mix several concerns: locale, currency display, sometimes a separate catalog scope, and a lot of configuration inheritance. On Medusa, the translation side of that now has a first-party home, so you're no longer choosing between a beta module and an external CMS for product copy.
Translation isn't the whole store-view model, though. Map each thing a store view does to its Medusa equivalent before you write any import code: language, currency, sales channel, price context. In our experience, store-view migrations fail when someone assumes "one store view = one locale" and finds the exceptions in production. Most catalogs have attribute values that were overridden at store-view level for reasons nobody remembers. Export those overrides and look at them before you decide what becomes a translation and what becomes data.
One fix in this release matters directly here: cached localized reads and the admin translation list are now invalidated when a translation is created, updated or deleted (#17746). If you were on the beta module and saw editors complain that their changes didn't appear, this was probably the cause. Test it again after upgrading.
Cross-module joins replace the Index Module
Medusa now resolves cross-module queries with direct database joins rather than the Index Module, including in the /store/products route. The Index Module is deprecated and will be removed in a future release. If you registered it explicitly, remove it from modules in medusa-config.ts:
// remove if present:
// { resolve: "@medusajs/index" }
The notes say query.graph() calls and API filters that span module boundaries keep working without changes. Believe that, then check it. "Same results" and "same performance" are different claims, and the notes only make the first one. A filter that read from a denormalized index now runs as a join against your real tables. On a catalog of a few thousand products you won't notice. On a large catalog with deep category trees and many linked custom modules, profile your heaviest storefront listing queries before and after the upgrade.
Two related type fixes make the query surface better to work with: the q free-text filter is now allowed in query.graph filters (#17775), and you can filter on nullable json columns and nullable to-many relations (#16892). If you had as any casts around these, you can remove them.
There is a security fix, and patches for older versions
If you enabled the Index Module feature flag, this release fixes the handling of ? characters in query parameters passed to /store/products and /store/product-variants (#17773). The notes don't assign a severity, but they do "urge" teams that can't upgrade to apply a version-specific patch. Patches are published for 2.15.3–2.15.5, 2.16.0, 2.17.0–2.21.1, 2.21.2–2.22.4 and 2.22.5–2.22.6.
The patch is a stopgap. v2.22.7 is the current release and the one to aim for. It also bumps proxy-addr to 2.0.8 for CVE-2026-90711 (#17762) and sets security headers on HTTP responses (#17763). That last change is easy to miss and can surprise you if your admin or storefront relies on being framed or on permissive defaults. Check your response headers in staging.
Promotion events give you a hook Magento never had cleanly
Medusa now emits events when promotions, promotion rules and campaigns are created, updated or deleted (#17136). Subscribers can react to them.
On Magento 2, finding out when a cart price rule changed usually means plugins on the repository or observers that miss changes made through the admin's mass actions. Here it's a supported event. Practical uses: invalidating cached promo banners on the storefront, notifying a merchandiser's channel when a campaign budget changes, or keeping an external pricing feed in sync. That's ordinary workflow automation, not anything clever. Check the exact event names in the Medusa docs before you write subscribers. Don't guess at them.
If you're migrating catalog price rules, keep the distinction in mind. Most catalog-level discounts belong in price lists. Cart-level conditional logic belongs in promotions. Several fixes in this release land squarely on that boundary:
- Spend campaign budgets are now checked against all adjustments in a cart, and promotions that don't fully fit are skipped (#17599).
- Cart shipping methods are re-priced after promotions are recomputed (#17070).
- Buy-get discounts no longer apply to non-discountable items (#17443).
- Overlapping buy-get promotions can no longer reuse units consumed by another promotion (#17134).
- Rolling back a price list price update now restores the previous prices (#17062).
Each of these is a case where totals were wrong before. If your store's totals changed after the upgrade, check this list first.
The upgrade and regression checklist
For teams already on Medusa:
- Branch and upgrade every
@medusajs/*package to 2.22.7 together. Don't mix versions. - Remove
@medusajs/indexfrommodulesif it's registered, and remove the Index Module feature flag from your environment. - Run migrations in staging against a recent production snapshot, not seed data.
- Diff storefront listing responses. Hit
/store/productswith your real filter combinations before and after the upgrade, then compare result sets and response times. - Replay promotion scenarios. Re-run your known cart fixtures: stacked codes, buy-get, spend campaigns near their budget limit, carts with non-discountable items. Totals that change are expected. Read each one against the fix list above before accepting it.
- Check shipping totals on discounted carts. The re-pricing fix changes when shipping is calculated.
- Edit a translation and read it back through the storefront to confirm the cache is invalidated.
- Inspect response headers on the storefront, admin and any embedded views.
- Test refunds against your payment provider's sandbox. Rejected refunds no longer record refund transactions (#17748), and the refunded amount is recomputed on provider failure (#17489). Reconciliation reports may shift.
- If you use SSO with RBAC, check that first-user provisioning gets the super admin role (#17782).
If you can't do all of that this week, apply the published patch for your version now and schedule the full upgrade.
If you're still on Magento 2 and weighing a move, this release removes one of the bigger objections for multilingual stores. It doesn't remove the work of mapping store views and price rules. That mapping is the bulk of a Magento 2 to Medusa migration, and it's worth scoping before anyone writes an importer. If you want a second pair of eyes on that, or on a 2.22.7 upgrade, get in touch.
Need this done on a real stack?
Magento 2, Adobe Commerce, migrations to Medusa.js or Vendure, enterprise Next.js, WordPress, and AI automation.
Contact us