v2.15.1 includes missing PRs from 2.15.0
This patch release includes several PRs that were accidentally omitted from the 2.15.0 release due to a process issue. Users who installed 2.15.0 should upgrade to get the intended changes from that version.
Highlights
Includes missing PRs from 2.15.0 release
Due to an issue during the release process of 2.15.0, several PRs listed in the release notes weren't included. If you've already installed 2.15.0, you might have experienced behavior matching this description. If you want the changes listed in the release notes of said version, you should install this one instead. The issue in the release process has already been corrected.
Chores
- chore(docs): Generated + Updated UI Reference (automated) by @app/github-actions in #15368
- chore(docs): Update version in documentation (automated) by @app/github-actions in #15367
- chore(docs): doc changes for next release (automated) by @shahednasser in #15257
Full Changelog: v2.15.0...v2.15.1
Source: original entry ↗
More from Medusa
Follow Medusa to get its new changes in your feed and email digest.
Performance Improvement for Search Route
The /store/search route now restricts field retrieval to only those defined on the index being searched, preventing data hydration outside the index for better performance. This release includes multiple bug fixes for search indexing, caching, promotions, payments, and dashboard internationalization.
v2.21.1: Search Module
Introduces a new Search Module that lets you manage and search through indexes for any data model, with built-in PostgreSQL and Medusa Cloud providers. Also includes improvements to the loyalty plugin's store credit features, new admin translations for Finnish and Swedish, and numerous bug fixes across authentication, payments, inventory, and shipping.
Strict allowed fields in Store API and Exported Admin Components
Store API routes now enforce a strict allowed-fields list, returning only explicitly declared fields and relations to prevent unintended data exposure. Disallowed fields are silently stripped; use the allowFields middleware to re-expose specific fields if needed.