Medusa: v2.13.1: Fixes regression with totals on order listing

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

🔧 Bug Fixes 4

⚡ Executive Summary (TL;DR)

Medusa v2.13.1. Source highlight: Fixes regression with totals on order listing

Visit Medusa Official Site ↗ Official Release Source ↗ All Medusa Releases 📡 Medusa RSS

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.

🔧 Bug Fixes & Patches (4)

fix(medusa): use http type for batch translation settings request
fix(core-flows): recompute adjustments for draft orders after changes are added
fix(order): item relation loading in select-in path
docs: fix references pipeline + generate references for v2.13.0

📄 View Raw Release Notes (Original Developer Log)

## Highlights ### Fixes regression with totals on order listing This release fixes a bug introduced in v2.13.0 around total fields selection when listing orders. The bug occurs when loading order items with their relations using the `select-in` strategy: 1. The code maps field selections from `items.*` to `items.item.*` to load OrderLineItem data 2. However, critical OrderItem fields like `quantity` live on items.detail, not on items.item 3. These fields were being dropped during the mapping process 4. Without quantity data, the order totals couldn't be calculated correctly The `select-in` strategy is used when listing orders with pagination options, which is for example used in the `GET /admin/orders` and `GET /admin/draft-orders` endpoints. This fix adds compensatory logic that ensures when `items.item.*` fields are selected, the corresponding `items.*` fields are also selected or preserved. This prevents the data required for order calculations from being removed. ## Bugs * fix(medusa): use http type for batch translation settings request by @shahednasser in https://github.com/medusajs/medusa/pull/14612 * fix(core-flows): recompute adjustments for draft orders after changes are added by @fPolic in https://github.com/medusajs/medusa/pull/14511 * fix(order): item relation loading in select-in path by @fPolic in https://github.com/medusajs/medusa/pull/14629 ## Documentation * docs: changes for v2.13.0 by @shahednasser in https://github.com/medusajs/medusa/pull/14524 * chore(docs): Updated API Reference (automated) by @github-actions[bot] in https://github.com/medusajs/medusa/pull/14609 * docs: fix references pipeline + generate references for v2.13.0 by @shahednasser in https://github.com/medusajs/medusa/pull/14623 ## Chores * chore(docs): Updated UI Reference (automated) by @github-actions[bot] in https://github.com/medusajs/medusa/pull/14608 * chore(docs): Generated DML JSON files (automated) by @github-actions[bot] in https://github.com/medusajs/medusa/pull/14607 * chore(docs): Update version in documentation (automated) by @github-actions[bot] in https://github.com/medusajs/medusa/pull/14611 * chore(medusa): default medusa policies by @carlos-r-l-rodrigues in https://github.com/medusajs/medusa/pull/14542 **Full Changelog**: https://github.com/medusajs/medusa/compare/v2.13.0...v2.13.1

← Older Version Medusa v2.13.0 Newer Version → Medusa v2.13.2