Impact Score: 5/10
Medusa v1.20.7 โ 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.
โก Executive Summary (TL;DR)
Medusa v1.20.7. Source highlight: Duplicate workflow registration no longer throws
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 (1)
- chore(ap-ref v1.x): add v2 rewrite + remove versioning snippets
๐ง Bug Fixes & Patches (6)
- fix(workflows-sdk): workflow registration
- fix(medusa): TX isolation level in batch job subscriber
- docs: fix code snippet for webpack custom configurations
- docs(v1.x): fix rewrites of api-reference
- docs: fix example code block
- docs(v1.x): fix link to stripe plugin
๐ View Raw Release Notes (Original Developer Log)
<!--

# Version 1.20.7
This version squashes a few bugs, including batch job processing and the workflow registration mechanism.
CMS_BREAK -->
## Highlights
### Duplicate workflow registration no longer throws
Workflows are not utilized in v1.x, however our core package comes with a few workflows for v2.0. We are currently investigating an issue with checking for duplicate workflow registrations, but we can safely remove this check in v1.x, as it will never affect users using these versions.
### Isolation level in batch job subscriber
The transaction isolation level set by the batch job processing subscriber has been changed from the default "READ COMMITTED" to "REPEATABLE READ" to ensure correct data in long-running job processors.
This was always the intention, but the "REPEATABLE READ" level set in the batch job strategies was overwritten by the default level set in the subscriber calling the strategy. This happens because the subscriber initiates a transaction with the default level that is then reused within the strategies.
## Bugs
* fix(workflows-sdk): workflow registration by @carlos-r-l-rodrigues in https://github.com/medusajs/medusa/pull/7590
* fix(medusa): TX isolation level in batch job subscriber by @olivermrbl in https://github.com/medusajs/medusa/pull/7661
## Docs
* docs(v1.x): use correct branch name by @shahednasser in https://github.com/medusajs/medusa/pull/7233
* docs: fix code snippet for webpack custom configurations by @shahednasser in https://github.com/medusajs/medusa/pull/7188
* docs(v1.x): fix rewrites of api-reference by @shahednasser in https://github.com/medusajs/medusa/pull/7318
* docs: fix example code block by @chiuwah in https://github.com/medusajs/medusa/pull/7453
* docs(v1.x): fix link to stripe plugin by @shahednasser in https://github.com/medusajs/medusa/pull/7557
## Chores
* chore(v1.x): fix build command in docs-util by @shahednasser in https://github.com/medusajs/medusa/pull/7280
* chore(ap-ref v1.x): add v2 rewrite + remove versioning snippets by @shahednasser in https://github.com/medusajs/medusa/pull/7305
## New Contributors
* @chiuwah made their first contribution in https://github.com/medusajs/medusa/pull/7453
**Full Changelog**: https://github.com/medusajs/medusa/compare/v1.20.6...v1.20.7