Impact Score: 5/10
Medusa: v2.12.1: Fix regression in events system
Source available — automated, not human-reviewed
Component: medusajs · Channel: stable. Automated analysis, not a compatibility certification. How this works.
Analysis updated: 2026-11-01.
⚡ Executive Summary (TL;DR)
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.
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.
⚡ Performance & Enhancements (1)
- docs: improve CORS troubleshooting guide
🔧 Bug Fixes & Patches (3)
- fix(order): Add composite unique index on order_item version:item_id
- fix(): event emitting
- chore: fixes to TSDocs
📄 View Raw Release Notes (Original Developer Log)
## Highlights
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.
However, this unintentionally broke instances running in `server` mode. Historically, server instances have not registered subscribers, only worker instances have. With the new optimization, these instances incorrectly determined that no subscribers existed for all emitted events and therefore skipped emission entirely.
**As a result, applications running version 2.12.0 in server mode have effectively emitted no events.**
If you have already upgraded to 2.12.0 and are using server instances, we strongly recommend validating whether any critical events have been missed since the upgrade and, if necessary, processing them manually.
This release also contains a migration, so you need to run the migration script after upgrading:
```
npx medusa db:migrate
```
## Bugs
* fix(order): Add composite unique index on order_item version:item_id by @NicolasGorga in https://github.com/medusajs/medusa/pull/14164
* fix(): event emitting by @adrien2p in https://github.com/medusajs/medusa/pull/14196
## Documentation
* docs: docs for next release by @shahednasser in https://github.com/medusajs/medusa/pull/14110
* chore(docs): Generated DML JSON files (automated) by @github-actions[bot] in https://github.com/medusajs/medusa/pull/14180
* chore(docs): Updated UI Reference (automated) by @github-actions[bot] in https://github.com/medusajs/medusa/pull/14181
* chore(docs): Generated References (automated) by @github-actions[bot] in https://github.com/medusajs/medusa/pull/14182
* docs: generate API reference for 2.12.0 by @shahednasser in https://github.com/medusajs/medusa/pull/14185
* docs: strapi integration guide by @shahednasser in https://github.com/medusajs/medusa/pull/14075
* docs: track code copy + AI assistant event by @shahednasser in https://github.com/medusajs/medusa/pull/14193
* docs: improve CORS troubleshooting guide by @shahednasser in https://github.com/medusajs/medusa/pull/14194
## Chores
* chore(docs): Update version in documentation (automated) by @github-actions[bot] in https://github.com/medusajs/medusa/pull/14179
* chore: fixes to TSDocs by @shahednasser in https://github.com/medusajs/medusa/pull/14186
**Full Changelog**: https://github.com/medusajs/medusa/compare/v2.12.0...v2.12.1