* Include locale field for traslations on tax line workflows
* Translate tax lines in getItemTaxLinesStep with new util
* Update tax calculation context, so that we pass locale to third party tax providers if they want to return translated tax rates
* Apply translations to tax lines on product and variant tax middlewares
* Cart management translations tests
* Update tax lines when order locale gets updated
* Add changeset
* Get tranlsated tax lines step
* Fix wording
* Mutate ref directly
* Update order tax lines translations upon order locale change
* Claims translations tests
* Update tax lines upon draft order locale update
* Exchange tests for tax lines translations
* Order edits test for tax line translation
* Add tests for shipping methods tax line translations on various order flows
* Returns shipping method translations tests
* Execute update in parallel
* Use TranslationFeatureFlag.key
* Fix feature flag import
* Add @medusajs/medusa dependency for feature flag usage
* Revert "Add @medusajs/medusa dependency for feature flag usage"
This reverts commit e8897aed0a88f83c1034ac73e817e4222250a2c9.
* Use feature flag string directly
* Fix test
* Parallelize tax line translations application
* Avoid throwing prices not found error when line item is custom unit price
* Add changeset
* Avoid throwing upo variant price validation for custom priced item variants
## Summary
**What** — What changes are introduced in this PR?
Fix small typo in file import in the Meta product feed tutorial
**Why** — Why are these changes relevant or necessary?
The typo in the import path causes confusion when following the Meta product feed tutorial and can lead to runtime or build errors for developers implementing the feature.
Fixing it ensures the documentation matches the actual file structure and improves the developer experience.
**How** — How have these changes been implemented?
The incorrect import path in the tutorial was corrected to reference the proper file name.
No logic or behavior was changed—only the documentation example was updated.
**Testing** — How have these changes been tested, or how can the reviewer test the feature?
This change affects documentation only.
---
## Examples
Not applicable. This PR only corrects a typo in the documentation.
## Checklist
Please ensure the following before requesting a review:
- [ ] I have added a **changeset** for this PR
- Every non-breaking change should be marked as a **patch**
- To add a changeset, run `yarn changeset` and follow the prompts
- [ ] The changes are covered by relevant **tests**
- [x] I have verified the code works as intended locally
- [x] I have linked the related issue(s) if applicable
---
## Additional Context
Resolves#14522
---
> [!NOTE]
> Updates the product feed tutorial to correct a typo in an import path.
>
> - In `src/workflows/generate-product-feed.ts` snippet within `page.mdx`, change `./steps/build-product-field-xml` to `./steps/build-product-feed-xml`. Documentation-only; no runtime code modified.
>
> <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 560f3a356f696be1d05fca9931593daff3217059. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup>
## Summary
**What** — What changes are introduced in this PR?
Export Zod as a dependency of `@medusajs/framework`.
Closes DX-2414
**Why** — Why are these changes relevant or necessary?
Zod is an essential part of Medusa development. We use it in the core and developers use it in their customizations.
Developers using pnpm won't have access to Zod, as it's not a top-level dependency. While they can install any version, since Zod is an essential aspect of our framework, it's more convenient that we export it and make it accessible to developers.
**How** — How have these changes been implemented?
1. Add Zod as a dependency in `@medusajs/deps` and export it in `@medusajs/framework`
2. Change imports of Zod across projects to import from `@medusajs/framework` and remove the Zod dependency.
> Note: this change doesn't cover admin extensions (and our related packages), as they're not related to the Medusa framework and using Zod in them isn't part of the conventions we document.
Developers can import Zod like this now:
```ts
import { z } from "@medusajs/framework/zod"
```
**Testing** — How have these changes been tested, or how can the reviewer test the feature?
Use the following import in a Medusa project to create an validate zod schemas:
```bash
import { MedusaRequest, MedusaResponse } from "@medusajs/framework/http";
import { z } from "@medusajs/framework/zod"
export const PostCustomSchema = z.object({
name: z.string(),
})
type PostCustomSchema = z.infer<typeof PostCustomSchema>
export async function POST(
req: MedusaRequest<PostCustomSchema>,
res: MedusaResponse
) {
res.json({
message: `Hello, ${req.validatedBody.name}`
})
}
// in middleware
import { defineMiddlewares, validateAndTransformBody } from "@medusajs/framework/http"
import { PostCustomSchema } from "./admin/custom/route"
export default defineMiddlewares({
routes: [
{
matcher: "/custom",
middlewares: [validateAndTransformBody(PostCustomSchema)],
},
],
})
```
---
## Examples
-
---
## Checklist
Please ensure the following before requesting a review:
- [x] I have added a **changeset** for this PR
- Every non-breaking change should be marked as a **patch**
- To add a changeset, run `yarn changeset` and follow the prompts
- [ ] The changes are covered by relevant **tests**
- [x] I have verified the code works as intended locally
- [x] I have linked the related issue(s) if applicable
---
## Additional Context
-
Automated changes by [create-pull-request](https://github.com/peter-evans/create-pull-request) GitHub action
---
> [!NOTE]
> Applies patch updates to the Medusa UI stack across the monorepo.
>
> - Bumps `@medusajs/icons` to `2.12.5`, `@medusajs/ui` to `4.0.33`, and `@medusajs/ui-preset` to `2.12.5`
> - Updates affected apps/packages: `api-reference`, `book`, `cloud`, `resources`, `ui`, `user-guide`, `docs-ui`, `tailwind`, and `types`
> - Refreshes `yarn.lock` accordingly
>
> <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 756527915a20240054463bd83b93888d5dc0f5da. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup>
Co-authored-by: Oli Juhl <59018053+olivermrbl@users.noreply.github.com>
* fix(build): Introduce a schema only flag for more heavy light weight loading
* fix(build): cleanup and tests
* Create shy-snails-raise.md
* fix(build): cleanup
* feat(DML): Add a new translatable property modifier applicable on text
* feat(DML): Add a new translatable property modifier applicable on text
* feat(DML): Add a new translatable property modifier applicable on text
* Create gold-bobcats-decide.md
* feat(DML): Add a new translatable property modifier applicable on text
* feat(DML): Add a new translatable property modifier applicable on text
* simplification
Automated changes by [create-pull-request](https://github.com/peter-evans/create-pull-request) GitHub action
---
> [!NOTE]
> Updates Medusa UI-related dependencies to latest patch versions across the docs monorepo.
>
> - Bumps `@medusajs/icons` to `2.12.4` in `api-reference`, `book`, `cloud`, `resources`, `user-guide`, `docs-ui`, and `types`
> - Bumps `@medusajs/ui` to `4.0.32` in `api-reference`, `ui`, and `docs-ui`
> - Bumps `@medusajs/ui-preset` to `2.12.4` in `ui` and `tailwind`
> - Refreshes `yarn.lock` to reflect new versions
>
> <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit eac21c3aa042fd700e27e762e79200d76cf48ef5. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup>
Co-authored-by: Oli Juhl <59018053+olivermrbl@users.noreply.github.com>
1. Fix error when passing `--version` and installing Next.js storefront. The error is because the UI package doesn't follow the same versioning as other Medusa packages, so this will skip updating the version of the UI package.
2. Other: added error logging for installation errors
