Medusa v2.8.1stable Released May 15, 2025
Impact Score: 5/10

Medusa v2.8.1 โ€” Release Notes & Engineering Impact

Source available โ€” automated, not human-reviewed

Component: medusajs ยท Channel: stable. Automated analysis, not a compatibility certification. How this works.

Analysis updated: 2026-11-01.

Compatibility not verified โ€” check source notes
๐Ÿ“„ .MD
โšก Executive Summary (TL;DR)

Medusa v2.8.1. Source highlight: **Fixes a regression introduced in v2.8.0**

Who Does This Impact? (Role-Based Analysis)

๐Ÿ’ป Software Engineers & Devs

Check the source notes against the package and APIs you use before upgrading.

๐Ÿ“Š Product & Engineering Leads

Use the documented changes to assess relevance to your product; release frequency alone is not a quality measure.

โš™๏ธ DevOps & Security

Verify the target version, runtime requirements and rollback procedure in the official documentation.

โœจ New Features & Capabilities (2)

  • feat: create CSV normalizer to normalize a CSV file
  • chore(types,utils): add featureFlag and version tags

โšก Performance & Enhancements (1)

  • Chore/test runner improvements

๐Ÿ”ง Bug Fixes & Patches (4)

  • fix(workflows-sdk): Miss match context usage within run as step
  • fix(index): query builder handle json array
  • fix: returned updates order in upsertWithReplace
  • docs: fix client side error in references
๐Ÿ“„ View Raw Release Notes (Original Developer Log)
<!-- ![2-8-1](https://gh-release-images.s3.eu-north-1.amazonaws.com/v2-8-1.png) # v2.8.1: Fixes regression related to product variant price updates This release fixes a regression introduced in v2.8.0 related to product ordering in service responses, leading to incorrect pricing updates on products. CMS_BREAK --> ## Highlights **Fixes a regression introduced in v2.8.0** In v2.8.0, we unintentionally introduced a regression that affected ordering products returned from the product module service. This broke workflows (e.g. `updateProductsWorkflow`) that rely on consistent ordering for subsequent operations such as applying price updates. This release brings back the correct ordering behavior and resolves the issue. **We strongly recommend upgrading to v2.8.1 as soon as possible to avoid incorrect data.** ## Features * feat: create CSV normalizer to normalize a CSV file by @thetutlage in https://github.com/medusajs/medusa/pull/12396 ## Bugs * fix(workflows-sdk): Miss match context usage within run as step by @adrien2p in https://github.com/medusajs/medusa/pull/12449 * fix(index): query builder handle json array by @carlos-r-l-rodrigues in https://github.com/medusajs/medusa/pull/12480 * fix: returned updates order in upsertWithReplace by @peterlgh7 in https://github.com/medusajs/medusa/pull/12486 ## Documentation * docs: tax provider updates for next release by @shahednasser in https://github.com/medusajs/medusa/pull/12431 * docs: update read-only links by @shahednasser in https://github.com/medusajs/medusa/pull/12468 * docs: fix client side error in references by @shahednasser in https://github.com/medusajs/medusa/pull/12475 ## Chores * chore(types,utils): add featureFlag and version tags by @shahednasser in https://github.com/medusajs/medusa/pull/12464 * Chore/test runner improvements by @adrien2p in https://github.com/medusajs/medusa/pull/12439 **Full Changelog**: https://github.com/medusajs/medusa/compare/v2.8.0...v2.8.1